Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe9a064d81ec3d940603b9b87a11e43a5459f21ca2f782568f797e0897b70a6

Tx prefix hash: 20c5ec9298bf0277640e96939791253e04f6f5ef80f4673de8cbc4ebbbb150e8
Tx public key: 86b11ba017b94e6f9ddb829a9191a1870e7a5c3bebccb774aca8ccc6324d417c
Timestamp: 1710585517 Timestamp [UCT]: 2024-03-16 10:38:37 Age [y:d:h:m:s]: 01:037:04:00:17
Block: 979524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287534 RingCT/type: yes/0
Extra: 0186b11ba017b94e6f9ddb829a9191a1870e7a5c3bebccb774aca8ccc6324d417c02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92dacb73e93441eaf59f001ac0d15f28caacd7efea46a117da022f3b2e137548 0.600000000000 1439559 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": 979534, "vin": [ { "gen": { "height": 979524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92dacb73e93441eaf59f001ac0d15f28caacd7efea46a117da022f3b2e137548" } } ], "extra": [ 1, 134, 177, 27, 160, 23, 185, 78, 111, 157, 219, 130, 154, 145, 145, 161, 135, 14, 122, 92, 59, 235, 204, 183, 116, 172, 168, 204, 198, 50, 77, 65, 124, 2, 17, 0, 0, 0, 10, 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