Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dd9af62ebd430f6d82b95dc58e40cabc3c73375eda009dfb05052f6556e94f8

Tx prefix hash: fdabde65db90d06e797d48268866bf603eded472a3440773da748e4f9261a02a
Tx public key: a4b96b9ae10cfd2b76d9237f636eba8dc8ebae8d1ec17dec37918a4dca37bf86
Timestamp: 1765503570 Timestamp [UCT]: 2025-12-12 01:39:30 Age [y:d:h:m:s]: 00:027:18:03:36
Block: 1431664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19888 RingCT/type: yes/0
Extra: 01a4b96b9ae10cfd2b76d9237f636eba8dc8ebae8d1ec17dec37918a4dca37bf86021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12380c5c8be27cd1392e19ccec521c3c95b1367f0637d175809c2077081c0a7e 0.600000000000 1920437 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": 1431674, "vin": [ { "gen": { "height": 1431664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12380c5c8be27cd1392e19ccec521c3c95b1367f0637d175809c2077081c0a7e" } } ], "extra": [ 1, 164, 185, 107, 154, 225, 12, 253, 43, 118, 217, 35, 127, 99, 110, 186, 141, 200, 235, 174, 141, 30, 193, 125, 236, 55, 145, 138, 77, 202, 55, 191, 134, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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