Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb77045d05345d35870c61966f98fd0f4bd5fab6bfc8f8f2ed54f78ec186ee8a

Tx prefix hash: 1dcc03b3a7754c40d3deb16e902ee59f348ae6eaf2bcd4d2d608773e9994eac0
Tx public key: ab214f80ac7d4768dd58b9a26fd5fc2970ba529947bb66f10e8131a0733e332e
Timestamp: 1756356670 Timestamp [UCT]: 2025-08-28 04:51:10 Age [y:d:h:m:s]: 00:082:18:20:24
Block: 1356048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59076 RingCT/type: yes/0
Extra: 01ab214f80ac7d4768dd58b9a26fd5fc2970ba529947bb66f10e8131a0733e332e0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 402463b2de5def2c9e0257d77678bc8700fb8514dccfce9b6b71645121a4d410 0.600000000000 1844053 of 15

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": 1356058, "vin": [ { "gen": { "height": 1356048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "402463b2de5def2c9e0257d77678bc8700fb8514dccfce9b6b71645121a4d410" } } ], "extra": [ 1, 171, 33, 79, 128, 172, 125, 71, 104, 221, 88, 185, 162, 111, 213, 252, 41, 112, 186, 82, 153, 71, 187, 102, 241, 14, 129, 49, 160, 115, 62, 51, 46, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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