Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9924d8a944b58ed05fd45231ec8653368669682411cd6dc6009a845d9dc41c6

Tx prefix hash: d114554c04d34f7f7db99989e03556fbd744e2303eca988248e63ef484973c1c
Tx public key: 72a2910853e7a905afb93d1fb4b681bfdcb27cef887130d7a09d0237f8e36cab
Timestamp: 1746749558 Timestamp [UCT]: 2025-05-09 00:12:38 Age [y:d:h:m:s]: 00:194:13:59:56
Block: 1278789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136782 RingCT/type: yes/0
Extra: 0172a2910853e7a905afb93d1fb4b681bfdcb27cef887130d7a09d0237f8e36cab021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35544a4bc7741a0c73c8c59f0c6513f6bb18c1d59e156741c7dca65f16ab33c 0.600000000000 1766160 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": 1278799, "vin": [ { "gen": { "height": 1278789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35544a4bc7741a0c73c8c59f0c6513f6bb18c1d59e156741c7dca65f16ab33c" } } ], "extra": [ 1, 114, 162, 145, 8, 83, 231, 169, 5, 175, 185, 61, 31, 180, 182, 129, 191, 220, 178, 124, 239, 136, 113, 48, 215, 160, 157, 2, 55, 248, 227, 108, 171, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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