Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e95b47d39617bb345b8f9e57d45bbda0ac30db4524f2d82875a7f6385bdb01

Tx prefix hash: 0f408279ac7503f5bdf9748820a2e7f7e68b3e22e46f3f9af2e9aa7cedae8a49
Tx public key: 7a18bfb124b157eb7081c85fad8164b1644659eed4a5abae9afbb3b88956fd90
Timestamp: 1577141552 Timestamp [UCT]: 2019-12-23 22:52:32 Age [y:d:h:m:s]: 05:015:02:12:18
Block: 30160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160956 RingCT/type: yes/0
Extra: 017a18bfb124b157eb7081c85fad8164b1644659eed4a5abae9afbb3b88956fd9002110000004be39b962a000000000000000000

1 output(s) for total of 487.605125441000 dcy

stealth address amount amount idx
00: 1f5ae16d36123db3d1cb0fc956711edb05298d7d8541198331e5333b155b9832 487.605125441000 49802 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": 30170, "vin": [ { "gen": { "height": 30160 } } ], "vout": [ { "amount": 487605125441, "target": { "key": "1f5ae16d36123db3d1cb0fc956711edb05298d7d8541198331e5333b155b9832" } } ], "extra": [ 1, 122, 24, 191, 177, 36, 177, 87, 235, 112, 129, 200, 95, 173, 129, 100, 177, 100, 70, 89, 238, 212, 165, 171, 174, 154, 251, 179, 184, 137, 86, 253, 144, 2, 17, 0, 0, 0, 75, 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