Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad73f50e4879e78f6ff2d0d08abd2ed0494353ddb401a9ea58ba88277da98bb4

Tx prefix hash: 285fca38bb562283d687fef298dfc011ca326a1ac985e60cfe389fc5b2237692
Tx public key: d4577aa62ba58cecde0bf9c4754bfbbbc25470f8d4629b8b1e6b8e146a1720ed
Timestamp: 1577371660 Timestamp [UCT]: 2019-12-26 14:47:40 Age [y:d:h:m:s]: 05:002:18:04:20
Block: 32253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151931 RingCT/type: yes/0
Extra: 01d4577aa62ba58cecde0bf9c4754bfbbbc25470f8d4629b8b1e6b8e146a1720ed0211000000044943cd9f000000000000000000

1 output(s) for total of 479.880697173000 dcy

stealth address amount amount idx
00: a65bed7aa0ef8bde6187e5a368c14c89bccd23cb44bbcc410a1ba32b20eb384c 479.880697173000 53610 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": 32263, "vin": [ { "gen": { "height": 32253 } } ], "vout": [ { "amount": 479880697173, "target": { "key": "a65bed7aa0ef8bde6187e5a368c14c89bccd23cb44bbcc410a1ba32b20eb384c" } } ], "extra": [ 1, 212, 87, 122, 166, 43, 165, 140, 236, 222, 11, 249, 196, 117, 75, 251, 187, 194, 84, 112, 248, 212, 98, 155, 139, 30, 107, 142, 20, 106, 23, 32, 237, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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