Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2662242ceb2a8b2c939bff257e47eb05a5727bb24efcb15ce7439b43769410d9

Tx prefix hash: 3bc4873bfaa4905d72afe0beb1c3ff04361dd503daf201caa21de439ebfa72f0
Tx public key: e19d704c05b9db936b7df45e1c3ebc60c1d864cac46c6d0e13e5e68d5fde49f7
Timestamp: 1709411865 Timestamp [UCT]: 2024-03-02 20:37:45 Age [y:d:h:m:s]: 01:033:12:51:15
Block: 969784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284967 RingCT/type: yes/0
Extra: 01e19d704c05b9db936b7df45e1c3ebc60c1d864cac46c6d0e13e5e68d5fde49f702110000000f0011055b000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 8c2e507970aeab7fecab28ade27c493ddb850d57c3dbd14fb5d4bef0fba3da67 0.600010000000 1429627 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": 969794, "vin": [ { "gen": { "height": 969784 } } ], "vout": [ { "amount": 600010000, "target": { "key": "8c2e507970aeab7fecab28ade27c493ddb850d57c3dbd14fb5d4bef0fba3da67" } } ], "extra": [ 1, 225, 157, 112, 76, 5, 185, 219, 147, 107, 125, 244, 94, 28, 62, 188, 96, 193, 216, 100, 202, 196, 108, 109, 14, 19, 229, 230, 141, 95, 222, 73, 247, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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