Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9689b520677249f0d2629a4db62d23832fba6ef6c748db5b33f08d58caae55

Tx prefix hash: 635c4289b8910d3951393c7541fa1914580e0c9c31e269c5211743e60578fd2a
Tx public key: 7e031ca6990f883fa4b1ea77b300704109517fa1eee2cf8f784b682663e784b7
Timestamp: 1761684117 Timestamp [UCT]: 2025-10-28 20:41:57 Age [y:d:h:m:s]: 00:010:06:53:29
Block: 1400029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7353 RingCT/type: yes/0
Extra: 017e031ca6990f883fa4b1ea77b300704109517fa1eee2cf8f784b682663e784b70211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4714e945c054f0656e1e51ec4f2e3e9b21c2d7bb2370c78f354342600a784f9c 0.600000000000 1888336 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": 1400039, "vin": [ { "gen": { "height": 1400029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4714e945c054f0656e1e51ec4f2e3e9b21c2d7bb2370c78f354342600a784f9c" } } ], "extra": [ 1, 126, 3, 28, 166, 153, 15, 136, 63, 164, 177, 234, 119, 179, 0, 112, 65, 9, 81, 127, 161, 238, 226, 207, 143, 120, 75, 104, 38, 99, 231, 132, 183, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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