Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72077dbe42ec32d2defe6395edf24de248ce1218846a6d08f4227c0a0539b2e

Tx prefix hash: 540d27ae18c50937989d27dc8254d39110370f1fa14ebf3d2ade64219eefdabe
Tx public key: c7529927d3fe9f9dff48d6f977f9ff4712f6d80a7b83b09462a2eb755d36019a
Timestamp: 1580569350 Timestamp [UCT]: 2020-02-01 15:02:30 Age [y:d:h:m:s]: 05:098:18:45:06
Block: 56585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222495 RingCT/type: yes/0
Extra: 01c7529927d3fe9f9dff48d6f977f9ff4712f6d80a7b83b09462a2eb755d36019a02110000000349b77a3d000000000000000000

1 output(s) for total of 398.598317456000 dcy

stealth address amount amount idx
00: 2f441768f2a8a9f3767f28d7031d47de3f4705389969f759ab1801327e9848e1 398.598317456000 104346 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": 56595, "vin": [ { "gen": { "height": 56585 } } ], "vout": [ { "amount": 398598317456, "target": { "key": "2f441768f2a8a9f3767f28d7031d47de3f4705389969f759ab1801327e9848e1" } } ], "extra": [ 1, 199, 82, 153, 39, 211, 254, 159, 157, 255, 72, 214, 249, 119, 249, 255, 71, 18, 246, 216, 10, 123, 131, 176, 148, 98, 162, 235, 117, 93, 54, 1, 154, 2, 17, 0, 0, 0, 3, 73, 183, 122, 61, 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