Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 274880e618901bdd64bafbcc6e2b2068aa59a52df0d6c5499dbed9e30c7e06d0

Tx prefix hash: 79804b24102dbf096bca8505cd74d9e98bdcc0d145ec26e6f8b231ce2b2bd74b
Tx public key: d8f2754affe2d4e10f41642d975215e2134081e4a51de41cd1c3c6afcd411ca9
Timestamp: 1744224715 Timestamp [UCT]: 2025-04-09 18:51:55 Age [y:d:h:m:s]: 00:272:16:58:26
Block: 1257880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192711 RingCT/type: yes/0
Extra: 01d8f2754affe2d4e10f41642d975215e2134081e4a51de41cd1c3c6afcd411ca90211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c9fdbd259ebe205595a14eab9533319da3406375747f6fd684a3b0487f34161 0.600000000000 1745011 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": 1257890, "vin": [ { "gen": { "height": 1257880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c9fdbd259ebe205595a14eab9533319da3406375747f6fd684a3b0487f34161" } } ], "extra": [ 1, 216, 242, 117, 74, 255, 226, 212, 225, 15, 65, 100, 45, 151, 82, 21, 226, 19, 64, 129, 228, 165, 29, 228, 28, 209, 195, 198, 175, 205, 65, 28, 169, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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