Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f8b3a818178ff22cad1f8b92a1df4908b28f0819d3cd753c910e0ffc9f962f

Tx prefix hash: 9a63839ad688434d6c097faf6b16c6c0395fc1d9e12e3594b9654e3272cd044a
Tx public key: f8f3de04fba3b9521d586b21b46fa537b480685288b56a9dbed044adc75842b5
Timestamp: 1765538816 Timestamp [UCT]: 2025-12-12 11:26:56 Age [y:d:h:m:s]: 00:011:08:08:51
Block: 1431959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8111 RingCT/type: yes/0
Extra: 01f8f3de04fba3b9521d586b21b46fa537b480685288b56a9dbed044adc75842b502110000000bd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5cc9d8e32cdc6aba0d4c7d2410e5fcd65ac0bea8f73bd15d518163aeaa3a24 0.600000000000 1920736 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": 1431969, "vin": [ { "gen": { "height": 1431959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5cc9d8e32cdc6aba0d4c7d2410e5fcd65ac0bea8f73bd15d518163aeaa3a24" } } ], "extra": [ 1, 248, 243, 222, 4, 251, 163, 185, 82, 29, 88, 107, 33, 180, 111, 165, 55, 180, 128, 104, 82, 136, 181, 106, 157, 190, 208, 68, 173, 199, 88, 66, 181, 2, 17, 0, 0, 0, 11, 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