Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dec131d0d471dbe0655759903709895180ffee61d5cc91f4744b6605fb7e6485

Tx prefix hash: 9d92b30e4adb2623e73e6655695f2e031f6750e9cc334d164608d5ff7d7df9fc
Tx public key: 3a2eba4c94cf28fcc5e232900c9652815e8ef84338ad6b3b1f60b15c67fb6a54
Timestamp: 1669436613 Timestamp [UCT]: 2022-11-26 04:23:33 Age [y:d:h:m:s]: 02:093:12:38:59
Block: 639260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588531 RingCT/type: yes/0
Extra: 013a2eba4c94cf28fcc5e232900c9652815e8ef84338ad6b3b1f60b15c67fb6a5402110000000171bd5189000000000000000000

1 output(s) for total of 4.675911178000 dcy

stealth address amount amount idx
00: b005629cd9073c3d17de7ea17e6015f11b9b2ac840b0da40dd1ae2ccc1fe24fb 4.675911178000 1078901 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 639270, "vin": [ { "gen": { "height": 639260 } } ], "vout": [ { "amount": 4675911178, "target": { "key": "b005629cd9073c3d17de7ea17e6015f11b9b2ac840b0da40dd1ae2ccc1fe24fb" } } ], "extra": [ 1, 58, 46, 186, 76, 148, 207, 40, 252, 197, 226, 50, 144, 12, 150, 82, 129, 94, 142, 248, 67, 56, 173, 107, 59, 31, 96, 177, 92, 103, 251, 106, 84, 2, 17, 0, 0, 0, 1, 113, 189, 81, 137, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8