Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efe966c4329cc695f041f0911e80df63d8f82be416b3fbeea2586fc6cd80ffb7

Tx prefix hash: 7498af6cf3a3bd75fd17db9f11385c7f247160d26972a6f9b716274b92b102c2
Tx public key: 99930b61a20224b69b165055c019f89d9e19fe91890b8c0ff299b453b890e447
Timestamp: 1577520465 Timestamp [UCT]: 2019-12-28 08:07:45 Age [y:d:h:m:s]: 04:314:04:26:50
Block: 33273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113806 RingCT/type: yes/0
Extra: 0199930b61a20224b69b165055c019f89d9e19fe91890b8c0ff299b453b890e4470211000000019159db1e000000000000000000

1 output(s) for total of 476.193252876000 dcy

stealth address amount amount idx
00: 96846783ad76148f71ad3fee581e319f7f1a91b7e6daa7ce86a8673006ea4f8f 476.193252876000 55672 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": 33283, "vin": [ { "gen": { "height": 33273 } } ], "vout": [ { "amount": 476193252876, "target": { "key": "96846783ad76148f71ad3fee581e319f7f1a91b7e6daa7ce86a8673006ea4f8f" } } ], "extra": [ 1, 153, 147, 11, 97, 162, 2, 36, 182, 155, 22, 80, 85, 192, 25, 248, 157, 158, 25, 254, 145, 137, 11, 140, 15, 242, 153, 180, 83, 184, 144, 228, 71, 2, 17, 0, 0, 0, 1, 145, 89, 219, 30, 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