Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b18449438be10f4399cf53eed68ac6cbf265009ea51af2b7ee20316c1a2404

Tx prefix hash: c8c73c1117f6fb6ea4f0dcd8c7ef2061fea8916ba29998ec2a14f805b61f0cfa
Tx public key: 551a08b8325068e313cf314dab690371c5a7b5ad246dae3bb9f3616a3876e1a2
Timestamp: 1705688523 Timestamp [UCT]: 2024-01-19 18:22:03 Age [y:d:h:m:s]: 01:098:02:37:11
Block: 938879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331237 RingCT/type: yes/0
Extra: 01551a08b8325068e313cf314dab690371c5a7b5ad246dae3bb9f3616a3876e1a20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ba9e6d66766a32bc41049da032b62a96adb9d3ec09998c3a2a42802edae5bc 0.600000000000 1396961 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": 938889, "vin": [ { "gen": { "height": 938879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ba9e6d66766a32bc41049da032b62a96adb9d3ec09998c3a2a42802edae5bc" } } ], "extra": [ 1, 85, 26, 8, 184, 50, 80, 104, 227, 19, 207, 49, 77, 171, 105, 3, 113, 197, 167, 181, 173, 36, 109, 174, 59, 185, 243, 97, 106, 56, 118, 225, 162, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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