Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1672cec85a2dfbd59234dd705c582575b93fc8cc6c718c122a817cf7c77f852f

Tx prefix hash: adbc34bebc068edaa9003bbe2df182b956a2ab8f7202b2d5e37dd3819b778358
Tx public key: c56c1b19d4f60d7cf16061d826ba2bf748cb3b2bc4aa77e02c36840ada1c7c68
Timestamp: 1766213667 Timestamp [UCT]: 2025-12-20 06:54:27 Age [y:d:h:m:s]: 00:002:13:55:44
Block: 1437554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1843 RingCT/type: yes/0
Extra: 01c56c1b19d4f60d7cf16061d826ba2bf748cb3b2bc4aa77e02c36840ada1c7c680211000000057b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f18decee162e872b606df9526fcb4b5adb6f340bb210189680443832e64c5f7b 0.600000000000 1926363 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": 1437564, "vin": [ { "gen": { "height": 1437554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f18decee162e872b606df9526fcb4b5adb6f340bb210189680443832e64c5f7b" } } ], "extra": [ 1, 197, 108, 27, 25, 212, 246, 13, 124, 241, 96, 97, 216, 38, 186, 43, 247, 72, 203, 59, 43, 196, 170, 119, 224, 44, 54, 132, 10, 218, 28, 124, 104, 2, 17, 0, 0, 0, 5, 123, 30, 81, 172, 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