Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1429ce1ed48c0cc3eda0b105dd3d41ed32590c44460be4f6c757b584c4bd10cc

Tx prefix hash: 0947595f3fdb07b7ffd16c5f916c70e6a1432753baa5ecd55e061d370b7d9670
Tx public key: d8355efcf51fd3abd4969c1c0fcfd6de6f4441b4b3008ee4e14f8ef788c70167
Timestamp: 1577577834 Timestamp [UCT]: 2019-12-29 00:03:54 Age [y:d:h:m:s]: 04:333:02:24:15
Block: 33922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127177 RingCT/type: yes/0
Extra: 01d8355efcf51fd3abd4969c1c0fcfd6de6f4441b4b3008ee4e14f8ef788c70167021100000083e39b962a000000000000000000

1 output(s) for total of 473.833402311000 dcy

stealth address amount amount idx
00: c729aac2ea7ee361c0c3c14f4c1c2851c83f7d96042c03ac31a34fb21c094b8a 473.833402311000 57011 of 0

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": 33932, "vin": [ { "gen": { "height": 33922 } } ], "vout": [ { "amount": 473833402311, "target": { "key": "c729aac2ea7ee361c0c3c14f4c1c2851c83f7d96042c03ac31a34fb21c094b8a" } } ], "extra": [ 1, 216, 53, 94, 252, 245, 31, 211, 171, 212, 150, 156, 28, 15, 207, 214, 222, 111, 68, 65, 180, 179, 0, 142, 228, 225, 79, 142, 247, 136, 199, 1, 103, 2, 17, 0, 0, 0, 131, 227, 155, 150, 42, 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