Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e62455cb2235e7285575e5ee80aff90113a8f05aca47c4c07743a70830227244

Tx prefix hash: 84c5eca9e9ed7007a8ddc07069c0bc9313a2f0ab92307123f7f3f7323d684139
Tx public key: bbfc6b3f1922a9c48fad7e9aeb0b0cf8660c3d92df0227b117f3fb05070b1241
Timestamp: 1738876237 Timestamp [UCT]: 2025-02-06 21:10:37 Age [y:d:h:m:s]: 00:317:22:28:32
Block: 1213622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225030 RingCT/type: yes/0
Extra: 01bbfc6b3f1922a9c48fad7e9aeb0b0cf8660c3d92df0227b117f3fb05070b124102110000000d27ff1f91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d673cc0d72c122acc9e8dc3448a20ad0fe7fc47405d59fc8884e40ccb32922d5 0.600000000000 1700401 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": 1213632, "vin": [ { "gen": { "height": 1213622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d673cc0d72c122acc9e8dc3448a20ad0fe7fc47405d59fc8884e40ccb32922d5" } } ], "extra": [ 1, 187, 252, 107, 63, 25, 34, 169, 196, 143, 173, 126, 154, 235, 11, 12, 248, 102, 12, 61, 146, 223, 2, 39, 177, 23, 243, 251, 5, 7, 11, 18, 65, 2, 17, 0, 0, 0, 13, 39, 255, 31, 145, 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