Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ab2210458055389d5b864fd6ba4e0ed3856c4891a512e06753525ceb221844

Tx prefix hash: f4764d1d6c9ef56ae3455ca4470d524807074fc7c6589d14beccc77c5684e570
Tx public key: 6a6d47a48c9d3298c62988432c7c2760db40fdc6ad49204f010bc3f2ea6cd59b
Timestamp: 1706089504 Timestamp [UCT]: 2024-01-24 09:45:04 Age [y:d:h:m:s]: 01:071:02:45:03
Block: 942197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311927 RingCT/type: yes/0
Extra: 016a6d47a48c9d3298c62988432c7c2760db40fdc6ad49204f010bc3f2ea6cd59b0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6ce19568d599d396abb041ef121d71b7d603170e3b115a168795364fd0a4e5e 0.600000000000 1400363 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": 942207, "vin": [ { "gen": { "height": 942197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6ce19568d599d396abb041ef121d71b7d603170e3b115a168795364fd0a4e5e" } } ], "extra": [ 1, 106, 109, 71, 164, 140, 157, 50, 152, 198, 41, 136, 67, 44, 124, 39, 96, 219, 64, 253, 198, 173, 73, 32, 79, 1, 11, 195, 242, 234, 108, 213, 155, 2, 17, 0, 0, 0, 9, 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