Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a651d82fe9cdc11caba01669834035ab0134164e4a223e3d851abab7b3687948

Tx prefix hash: 25b36ad1ee29164e39f7e1200a671e99505b2cf2ae38c9957d58f29a309c0d1a
Tx public key: d0aa7a73e22ba20f036f3e26d082074f92b7723cb2551cbe54d3d30980ef59d2
Timestamp: 1578130865 Timestamp [UCT]: 2020-01-04 09:41:05 Age [y:d:h:m:s]: 05:071:02:47:46
Block: 38415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200714 RingCT/type: yes/0
Extra: 01d0aa7a73e22ba20f036f3e26d082074f92b7723cb2551cbe54d3d30980ef59d2021100000015dcee4b4d000000000000000000

1 output(s) for total of 457.850298590000 dcy

stealth address amount amount idx
00: 4da2259dff286d47af92d438bf61cc8be85721af6d2733cc2ca3895731ffecf1 457.850298590000 65492 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": 38425, "vin": [ { "gen": { "height": 38415 } } ], "vout": [ { "amount": 457850298590, "target": { "key": "4da2259dff286d47af92d438bf61cc8be85721af6d2733cc2ca3895731ffecf1" } } ], "extra": [ 1, 208, 170, 122, 115, 226, 43, 162, 15, 3, 111, 62, 38, 208, 130, 7, 79, 146, 183, 114, 60, 178, 85, 28, 190, 84, 211, 211, 9, 128, 239, 89, 210, 2, 17, 0, 0, 0, 21, 220, 238, 75, 77, 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