Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa87e701f6c652e79b27b00612e888a6ebe938da3e3868327f81fe00084897e6

Tx prefix hash: 54bfa8c430a75d6533ae8d35106ccd01dc3e95adcedd503738ba269c268fa5be
Tx public key: d3a2e8fb6105f70ef6502ff7c020eef32f224258ba23bfe5e5b5542217cc9fff
Timestamp: 1727391320 Timestamp [UCT]: 2024-09-26 22:55:20 Age [y:d:h:m:s]: 00:117:10:50:09
Block: 1118831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83940 RingCT/type: yes/0
Extra: 01d3a2e8fb6105f70ef6502ff7c020eef32f224258ba23bfe5e5b5542217cc9fff02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67cc5969fbb64e8b7b2d15d41e356dcf7f5d28d719e8c1df51f05d2eccba1517 0.600000000000 1600164 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": 1118841, "vin": [ { "gen": { "height": 1118831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67cc5969fbb64e8b7b2d15d41e356dcf7f5d28d719e8c1df51f05d2eccba1517" } } ], "extra": [ 1, 211, 162, 232, 251, 97, 5, 247, 14, 246, 80, 47, 247, 192, 32, 238, 243, 47, 34, 66, 88, 186, 35, 191, 229, 229, 181, 84, 34, 23, 204, 159, 255, 2, 17, 0, 0, 0, 3, 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