Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6474d2fd85201df4443b2ecef98e646da67440c2dd2fa37b88bd6f4fabb57a3

Tx prefix hash: 5957c0ed363e24080b49cf46efdc301bc0e5e167936038ae073b996984ded7df
Tx public key: 390e7c766052ca9cbbee3c5378c3362def8d9bcb89dd37cb2891be8cb3e69dfd
Timestamp: 1715285683 Timestamp [UCT]: 2024-05-09 20:14:43 Age [y:d:h:m:s]: 00:264:03:40:29
Block: 1018471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188797 RingCT/type: yes/0
Extra: 01390e7c766052ca9cbbee3c5378c3362def8d9bcb89dd37cb2891be8cb3e69dfd0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76221da2cdc6dcb22cc7ab8c8bc224f84c0244de25f5ae55855e7a1952d0e1ab 0.600000000000 1482260 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": 1018481, "vin": [ { "gen": { "height": 1018471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76221da2cdc6dcb22cc7ab8c8bc224f84c0244de25f5ae55855e7a1952d0e1ab" } } ], "extra": [ 1, 57, 14, 124, 118, 96, 82, 202, 156, 187, 238, 60, 83, 120, 195, 54, 45, 239, 141, 155, 203, 137, 221, 55, 203, 40, 145, 190, 140, 179, 230, 157, 253, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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