Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed7f1338033a638bd6e3cebcf3508bad67ee98e917a2fd35f66edf9e456e40d

Tx prefix hash: 8a11195eb9f48739c933049fd7955836bd9b6f288c73e6aee375cbbf202b8084
Tx public key: 11eb101c1c7005f6e4c12957f12e34b6c3205237c7714f32dfdea88e33acf4dd
Timestamp: 1581743195 Timestamp [UCT]: 2020-02-15 05:06:35 Age [y:d:h:m:s]: 04:285:19:17:43
Block: 65494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096260 RingCT/type: yes/0
Extra: 0111eb101c1c7005f6e4c12957f12e34b6c3205237c7714f32dfdea88e33acf4dd0211000000284943cd9f000000000000000000

1 output(s) for total of 372.384846977000 dcy

stealth address amount amount idx
00: b1a8594f1c426f08a97be171276e38bca3db4505fbad2e765ffc44d87bbfd082 372.384846977000 120745 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": 65504, "vin": [ { "gen": { "height": 65494 } } ], "vout": [ { "amount": 372384846977, "target": { "key": "b1a8594f1c426f08a97be171276e38bca3db4505fbad2e765ffc44d87bbfd082" } } ], "extra": [ 1, 17, 235, 16, 28, 28, 112, 5, 246, 228, 193, 41, 87, 241, 46, 52, 182, 195, 32, 82, 55, 199, 113, 79, 50, 223, 222, 168, 142, 51, 172, 244, 221, 2, 17, 0, 0, 0, 40, 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