Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12399232687b8ea9ad60720d2ab63b770c5b94110aa5859ba8029b20b829b0f8

Tx prefix hash: 1f878f3368e2c90394fda6191424c4186a66b59651cf20e7d323b2ba084ba058
Tx public key: afe9ff89d09345c664935073967f6baaf8f9c7efeb2ae71bb51da0d78c8253cb
Timestamp: 1587537880 Timestamp [UCT]: 2020-04-22 06:44:40 Age [y:d:h:m:s]: 04:072:16:43:09
Block: 95183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 962055 RingCT/type: yes/0
Extra: 01afe9ff89d09345c664935073967f6baaf8f9c7efeb2ae71bb51da0d78c8253cb0211000000074ac5aa02000000000000000000

1 output(s) for total of 296.906685370000 dcy

stealth address amount amount idx
00: e22fa37193ad8f002a511ef050de52a3baa8dc55960aa47fb14913dcfc1fbcdf 296.906685370000 169111 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": 95193, "vin": [ { "gen": { "height": 95183 } } ], "vout": [ { "amount": 296906685370, "target": { "key": "e22fa37193ad8f002a511ef050de52a3baa8dc55960aa47fb14913dcfc1fbcdf" } } ], "extra": [ 1, 175, 233, 255, 137, 208, 147, 69, 198, 100, 147, 80, 115, 150, 127, 107, 170, 248, 249, 199, 239, 235, 42, 231, 27, 181, 29, 160, 215, 140, 130, 83, 203, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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