Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7b60dba2642bfe8f7d1d904663436e23064f51521eec9909d9f61867a829f46

Tx prefix hash: 65456165f6248c0e916c6dc5d77249d3f4c90105a4686f42950a1c46e93c620f
Tx public key: c3c3e29cfdca83a75a86666ab5e1e39359553349ec9a2b53017ac1177c3cbb04
Timestamp: 1710669098 Timestamp [UCT]: 2024-03-17 09:51:38 Age [y:d:h:m:s]: 00:256:04:36:50
Block: 980215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183402 RingCT/type: yes/0
Extra: 01c3c3e29cfdca83a75a86666ab5e1e39359553349ec9a2b53017ac1177c3cbb040211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6115c9a9663d97416c4210c0d81c72e4c29bf7f7cc8717028e72a8d666630c7c 0.600000000000 1440280 of 15

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": 980225, "vin": [ { "gen": { "height": 980215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6115c9a9663d97416c4210c0d81c72e4c29bf7f7cc8717028e72a8d666630c7c" } } ], "extra": [ 1, 195, 195, 226, 156, 253, 202, 131, 167, 90, 134, 102, 106, 181, 225, 227, 147, 89, 85, 51, 73, 236, 154, 43, 83, 1, 122, 193, 23, 124, 60, 187, 4, 2, 17, 0, 0, 0, 5, 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