Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eeb57ce793e5e1ea5bc5e4b9b844fddc7ad8b6c1a8f435b2b62b74803343981

Tx prefix hash: fa4debbc6748879390fcebd505d74c1631a9e2c6b9be47b647b9a22a2da13add
Tx public key: d5512abb1001832ce8ed29d6dd4d41037325f822fa0d8e779dee8f0a6038ac40
Timestamp: 1583239590 Timestamp [UCT]: 2020-03-03 12:46:30 Age [y:d:h:m:s]: 04:297:12:39:10
Block: 75729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106819 RingCT/type: yes/0
Extra: 01d5512abb1001832ce8ed29d6dd4d41037325f822fa0d8e779dee8f0a6038ac400211000000cf56c366d3000000000000000000

1 output(s) for total of 344.412719977000 dcy

stealth address amount amount idx
00: cffa7a4e649eb60d94fc90df0d0343a428543cd84a5bc8452680a970e0cda039 344.412719977000 139699 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": 75739, "vin": [ { "gen": { "height": 75729 } } ], "vout": [ { "amount": 344412719977, "target": { "key": "cffa7a4e649eb60d94fc90df0d0343a428543cd84a5bc8452680a970e0cda039" } } ], "extra": [ 1, 213, 81, 42, 187, 16, 1, 131, 44, 232, 237, 41, 214, 221, 77, 65, 3, 115, 37, 248, 34, 250, 13, 142, 119, 157, 238, 143, 10, 96, 56, 172, 64, 2, 17, 0, 0, 0, 207, 86, 195, 102, 211, 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