Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3df22df78f7218e8ade2bd05dd5e8d9fe751d6c5410d0ee0d7a9efe785faf0

Tx prefix hash: 3895b9e2592bbd553cfd41ed2c9193e656d22568ad7c0fb7099d31e5c7ab29a6
Tx public key: f927c42156a6214c685a81c383563c71b7ad9751c38107dbbd52dfa095ebf238
Timestamp: 1759285712 Timestamp [UCT]: 2025-10-01 02:28:32 Age [y:d:h:m:s]: 00:086:14:21:13
Block: 1380127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62016 RingCT/type: yes/0
Extra: 01f927c42156a6214c685a81c383563c71b7ad9751c38107dbbd52dfa095ebf238021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b1d5db19516b0ff73a30a7f64ef8315ec945f726cc66c66ff411f13b7b47afc 0.600000000000 1868238 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": 1380137, "vin": [ { "gen": { "height": 1380127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b1d5db19516b0ff73a30a7f64ef8315ec945f726cc66c66ff411f13b7b47afc" } } ], "extra": [ 1, 249, 39, 196, 33, 86, 166, 33, 76, 104, 90, 129, 195, 131, 86, 60, 113, 183, 173, 151, 81, 195, 129, 7, 219, 189, 82, 223, 160, 149, 235, 242, 56, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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