Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999be28211390f5547a36e18e9bb168c1bcdb884960ca7f7f399a33736a2c318

Tx prefix hash: 689e555ec47b6dec155e5739aedc22a46e6a1e7af66d8bf29200f4c65e2276a3
Tx public key: 63f3a54374924f5c930bdc3155437b4d7e51a74e73ffbdd75d0abdaa6deb6c86
Timestamp: 1581667904 Timestamp [UCT]: 2020-02-14 08:11:44 Age [y:d:h:m:s]: 04:361:08:04:11
Block: 64771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150129 RingCT/type: yes/0
Extra: 0163f3a54374924f5c930bdc3155437b4d7e51a74e73ffbdd75d0abdaa6deb6c8602110000000356c366d3000000000000000000

1 output(s) for total of 374.444624804000 dcy

stealth address amount amount idx
00: 52a5e0c54b33663ee203ded1188ab3353c2b4ac23140b499574e78629cb3d086 374.444624804000 119482 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": 64781, "vin": [ { "gen": { "height": 64771 } } ], "vout": [ { "amount": 374444624804, "target": { "key": "52a5e0c54b33663ee203ded1188ab3353c2b4ac23140b499574e78629cb3d086" } } ], "extra": [ 1, 99, 243, 165, 67, 116, 146, 79, 92, 147, 11, 220, 49, 85, 67, 123, 77, 126, 81, 167, 78, 115, 255, 189, 215, 93, 10, 189, 170, 109, 235, 108, 134, 2, 17, 0, 0, 0, 3, 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