Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033fb0dc04180e05d5ca4991314911cd19b5be097e02bec4db6691ff78a17d59

Tx prefix hash: 5829648e2fa4dd0452dacaf378f4f627e3af00ad3aa5dee68a29d8bcb39bd9c9
Tx public key: 9405e41848f5dbf947edb4b4f97400cfda27ad7e3182d9959eff1207696ae1ec
Timestamp: 1705331713 Timestamp [UCT]: 2024-01-15 15:15:13 Age [y:d:h:m:s]: 01:324:04:04:31
Block: 935935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490545 RingCT/type: yes/0
Extra: 019405e41848f5dbf947edb4b4f97400cfda27ad7e3182d9959eff1207696ae1ec0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52f34d8b4f14abd7194eadd33ee76f50b66607624ea9b19e1a5668cbab5fd451 0.600000000000 1393955 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": 935945, "vin": [ { "gen": { "height": 935935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52f34d8b4f14abd7194eadd33ee76f50b66607624ea9b19e1a5668cbab5fd451" } } ], "extra": [ 1, 148, 5, 228, 24, 72, 245, 219, 249, 71, 237, 180, 180, 249, 116, 0, 207, 218, 39, 173, 126, 49, 130, 217, 149, 158, 255, 18, 7, 105, 106, 225, 236, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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