Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d2b9a036178e27c6ea84631c0f5092715c51dd3d60fa9e72b9fe27fd1f68bc

Tx prefix hash: 0c8831c4bd683eed2452299e145e418f515b69a0a285c78d14d98ef7d09fcce3
Tx public key: 62858ae2d0f87e3df76627b7087ad81886857dc6e52e109dac1bdde4c50b608e
Timestamp: 1663456048 Timestamp [UCT]: 2022-09-17 23:07:28 Age [y:d:h:m:s]: 03:044:09:30:06
Block: 590208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 811605 RingCT/type: yes/0
Extra: 0162858ae2d0f87e3df76627b7087ad81886857dc6e52e109dac1bdde4c50b608e02110000000efaf35c9c000000000000000000

1 output(s) for total of 6.798231713000 dcy

stealth address amount amount idx
00: 63fd8be7d0f39068a20e2c02ecbc7eb5a1ba60a79d4ea63ca3d9bb7e131d46de 6.798231713000 1024603 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": 590218, "vin": [ { "gen": { "height": 590208 } } ], "vout": [ { "amount": 6798231713, "target": { "key": "63fd8be7d0f39068a20e2c02ecbc7eb5a1ba60a79d4ea63ca3d9bb7e131d46de" } } ], "extra": [ 1, 98, 133, 138, 226, 208, 248, 126, 61, 247, 102, 39, 183, 8, 122, 216, 24, 134, 133, 125, 198, 229, 46, 16, 157, 172, 27, 221, 228, 197, 11, 96, 142, 2, 17, 0, 0, 0, 14, 250, 243, 92, 156, 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