Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05475651ebe234c01dede23705561b95d26e514e22bd2f83a7dc7a15d85dfd94

Tx prefix hash: f49bc894fc4ac98b327910e4422418486d6d06ae3d88f94064a2d4e1090810a7
Tx public key: 8fcc1db301883d2fd21a1c00d2bb71fe6011f4e76573cbd5b86616c8e3b8973c
Timestamp: 1712043120 Timestamp [UCT]: 2024-04-02 07:32:00 Age [y:d:h:m:s]: 01:270:17:57:32
Block: 991559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452277 RingCT/type: yes/0
Extra: 018fcc1db301883d2fd21a1c00d2bb71fe6011f4e76573cbd5b86616c8e3b8973c0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5786b71a126a93daae8e7f27683222971579fe654b0266ccaaf245d80a58b6da 0.600000000000 1451895 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": 991569, "vin": [ { "gen": { "height": 991559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5786b71a126a93daae8e7f27683222971579fe654b0266ccaaf245d80a58b6da" } } ], "extra": [ 1, 143, 204, 29, 179, 1, 136, 61, 47, 210, 26, 28, 0, 210, 187, 113, 254, 96, 17, 244, 231, 101, 115, 203, 213, 184, 102, 22, 200, 227, 184, 151, 60, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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