Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84a0eff0e0feb386fc8654b64a8685f648171e6a78c48034babc95bbd08c4b55

Tx prefix hash: 7d31ce5e3035aabdb93f917bcf33a6af2a330bfe186c3ee2a604a9eaf08e47e7
Tx public key: 0dc7c602697c0f0dd46870ebbf5bee4d43811358d3d43f202fd1a04ea43c82ed
Timestamp: 1729914745 Timestamp [UCT]: 2024-10-26 03:52:25 Age [y:d:h:m:s]: 00:162:09:35:09
Block: 1139717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115853 RingCT/type: yes/0
Extra: 010dc7c602697c0f0dd46870ebbf5bee4d43811358d3d43f202fd1a04ea43c82ed0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2600180c53415d68f34b5386e9fd00f81446c7ebc4a00396c4546ee9aeda01f1 0.600000000000 1623504 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": 1139727, "vin": [ { "gen": { "height": 1139717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2600180c53415d68f34b5386e9fd00f81446c7ebc4a00396c4546ee9aeda01f1" } } ], "extra": [ 1, 13, 199, 198, 2, 105, 124, 15, 13, 212, 104, 112, 235, 191, 91, 238, 77, 67, 129, 19, 88, 211, 212, 63, 32, 47, 209, 160, 78, 164, 60, 130, 237, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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