Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a32e8b58a5fb0e1af60bc03eeb47e21feaaef3f67f22fc5648c54e5fddd6f6c

Tx prefix hash: fec96452b7b0e06053838a7cd8c58ce18f275d084fdd52230e1010049ef03369
Tx public key: 92ecd32cf1c3a37e68ec0a0efbe027a17da9d77cd3f41b8110f73a1c344638f1
Timestamp: 1745460665 Timestamp [UCT]: 2025-04-24 02:11:05 Age [y:d:h:m:s]: 00:251:13:52:14
Block: 1268118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177584 RingCT/type: yes/0
Extra: 0192ecd32cf1c3a37e68ec0a0efbe027a17da9d77cd3f41b8110f73a1c344638f1021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19ce6580167364e60dfe1340b813fd6536d33bc102a0993db8dfd90f43b51813 0.600000000000 1755347 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": 1268128, "vin": [ { "gen": { "height": 1268118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19ce6580167364e60dfe1340b813fd6536d33bc102a0993db8dfd90f43b51813" } } ], "extra": [ 1, 146, 236, 211, 44, 241, 195, 163, 126, 104, 236, 10, 14, 251, 224, 39, 161, 125, 169, 215, 124, 211, 244, 27, 129, 16, 247, 58, 28, 52, 70, 56, 241, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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