Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59a473d7209be1543e11e54489e225cf1d8100eca8abcdd8e3eb42c04dd46b45

Tx prefix hash: 4eae376be922c85801164c2c506fd3c3348f442b3740c09721d804abb096d04c
Tx public key: 55d3de0a7c2eb2c600c16b1e0347f35b56824053bc4bb883a907396502e8fbfe
Timestamp: 1707324327 Timestamp [UCT]: 2024-02-07 16:45:27 Age [y:d:h:m:s]: 01:055:00:33:44
Block: 952465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300371 RingCT/type: yes/0
Extra: 0155d3de0a7c2eb2c600c16b1e0347f35b56824053bc4bb883a907396502e8fbfe02110000000510a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 026023cef31b812cc275df51619f16ed789c6f7b30793f194d782944e7089c91 0.600000000000 1411461 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": 952475, "vin": [ { "gen": { "height": 952465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "026023cef31b812cc275df51619f16ed789c6f7b30793f194d782944e7089c91" } } ], "extra": [ 1, 85, 211, 222, 10, 124, 46, 178, 198, 0, 193, 107, 30, 3, 71, 243, 91, 86, 130, 64, 83, 188, 75, 184, 131, 169, 7, 57, 101, 2, 232, 251, 254, 2, 17, 0, 0, 0, 5, 16, 161, 116, 143, 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