Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8707d3c65a218b91742e19066312917989f043b2c78ca46354c3bbf6d3b988d

Tx prefix hash: a688166a9623c16af38b938394d83ccb0907d7da3788ebe3198e2cefcc4b882a
Tx public key: 370ff19903b38a1ed616fb2fd85a26010b6e5464cec4543e733b285dcd9b02ac
Timestamp: 1745632011 Timestamp [UCT]: 2025-04-26 01:46:51 Age [y:d:h:m:s]: 00:255:22:55:43
Block: 1269528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180729 RingCT/type: yes/0
Extra: 01370ff19903b38a1ed616fb2fd85a26010b6e5464cec4543e733b285dcd9b02ac0211000000116c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f61e1f5aad5bdad6fd144d1c66e9e618760348e28d7b6a3e59b32aa8f524718e 0.600000000000 1756767 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": 1269538, "vin": [ { "gen": { "height": 1269528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f61e1f5aad5bdad6fd144d1c66e9e618760348e28d7b6a3e59b32aa8f524718e" } } ], "extra": [ 1, 55, 15, 241, 153, 3, 179, 138, 30, 214, 22, 251, 47, 216, 90, 38, 1, 11, 110, 84, 100, 206, 196, 84, 62, 115, 59, 40, 93, 205, 155, 2, 172, 2, 17, 0, 0, 0, 17, 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