Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95cdec3769245c11be27c663bbee333fc18e50eb77ce1f7146a9f1c24d8cd40

Tx prefix hash: bb86fc8784c61ab858d3a1c2c8518bbc34349020c7499f882ddf98bf40695873
Tx public key: 21f9b1060cb276c7bb99b33506f1c64da2f5065be6b018c271151e4c482cec44
Timestamp: 1729207285 Timestamp [UCT]: 2024-10-17 23:21:25 Age [y:d:h:m:s]: 00:156:19:58:24
Block: 1133886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111858 RingCT/type: yes/0
Extra: 0121f9b1060cb276c7bb99b33506f1c64da2f5065be6b018c271151e4c482cec44021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9253e625e2c0584bb7b64d53da4e17cdd1b26e36f6ba8412feb2a921903fb52 0.600000000000 1617099 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": 1133896, "vin": [ { "gen": { "height": 1133886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9253e625e2c0584bb7b64d53da4e17cdd1b26e36f6ba8412feb2a921903fb52" } } ], "extra": [ 1, 33, 249, 177, 6, 12, 178, 118, 199, 187, 153, 179, 53, 6, 241, 198, 77, 162, 245, 6, 91, 230, 176, 24, 194, 113, 21, 30, 76, 72, 44, 236, 68, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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