Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c3feadc80614288d3398e5411e5c320b33441645b412a3a43121d851853053b

Tx prefix hash: 567e01976d6759e19ddfaf489a207dadbaa8466c110f7106cd9f9ee13ed05977
Tx public key: 73e6b687e3c9b5d5dc807a7fa3db5218e9061c1352533b3431ba5ba8e52413c8
Timestamp: 1709495546 Timestamp [UCT]: 2024-03-03 19:52:26 Age [y:d:h:m:s]: 01:045:18:59:54
Block: 970473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293742 RingCT/type: yes/0
Extra: 0173e6b687e3c9b5d5dc807a7fa3db5218e9061c1352533b3431ba5ba8e52413c802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 763c1b77c84a2fc1ed4b23d8521d7d7179178a5409c09ce97c2d04fe914fc3a0 0.600000000000 1430326 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": 970483, "vin": [ { "gen": { "height": 970473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "763c1b77c84a2fc1ed4b23d8521d7d7179178a5409c09ce97c2d04fe914fc3a0" } } ], "extra": [ 1, 115, 230, 182, 135, 227, 201, 181, 213, 220, 128, 122, 127, 163, 219, 82, 24, 233, 6, 28, 19, 82, 83, 59, 52, 49, 186, 91, 168, 229, 36, 19, 200, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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