Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a5729f22d14a8877d1bbfe253906776dd8f799979811a8cd8e748892dcd251

Tx prefix hash: aa919f82cb3b8a4defce6d7bb0d1eafcdf7bd7b407d874b476a7885ac21c3d95
Tx public key: d0516f5d0a520ba7a561e6d73d7e34c933ed181359bb39bcbfaf2a4e00892495
Timestamp: 1765075725 Timestamp [UCT]: 2025-12-07 02:48:45 Age [y:d:h:m:s]: 00:015:01:25:26
Block: 1428121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10780 RingCT/type: yes/0
Extra: 01d0516f5d0a520ba7a561e6d73d7e34c933ed181359bb39bcbfaf2a4e0089249502110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a811bb00d954f72c3327d5f64e66f89879e298370ef96ed6df8f973543166b6 0.600000000000 1916830 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": 1428131, "vin": [ { "gen": { "height": 1428121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a811bb00d954f72c3327d5f64e66f89879e298370ef96ed6df8f973543166b6" } } ], "extra": [ 1, 208, 81, 111, 93, 10, 82, 11, 167, 165, 97, 230, 215, 61, 126, 52, 201, 51, 237, 24, 19, 89, 187, 57, 188, 191, 175, 42, 78, 0, 137, 36, 149, 2, 17, 0, 0, 0, 13, 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