Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6386aa456dc0b55f233b3b566dcebe85c29637ed3733c5c7fb3e6ac13712c03d

Tx prefix hash: 515b87aad467a0854f46396701add889d788fb26cc965cfd2dc066e0a0c777aa
Tx public key: 01e856720df9efbd09c8e4a0ab2c22d2c9d33d190bb5109faae80b57ec2950ec
Timestamp: 1724156367 Timestamp [UCT]: 2024-08-20 12:19:27 Age [y:d:h:m:s]: 00:238:22:41:11
Block: 1092023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170643 RingCT/type: yes/0
Extra: 0101e856720df9efbd09c8e4a0ab2c22d2c9d33d190bb5109faae80b57ec2950ec02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65056a98b6fb0a3efde7b060ea21a648d8a0525c3b3529b83724538716f3c525 0.600000000000 1566682 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": 1092033, "vin": [ { "gen": { "height": 1092023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65056a98b6fb0a3efde7b060ea21a648d8a0525c3b3529b83724538716f3c525" } } ], "extra": [ 1, 1, 232, 86, 114, 13, 249, 239, 189, 9, 200, 228, 160, 171, 44, 34, 210, 201, 211, 61, 25, 11, 181, 16, 159, 170, 232, 11, 87, 236, 41, 80, 236, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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