Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f81611e883e01ad691099ed15667531e6d0aa6bd527bb20a5cc9933edd9963f1

Tx prefix hash: 5f2d733a5cec297c7bbdac5185d34739dae7945dd77765b32261a7b6191a41a6
Tx public key: a99bee776cb27e360af087c22516ecaf7af325401efc7c650d3d2d9f870f4cb3
Timestamp: 1712272631 Timestamp [UCT]: 2024-04-04 23:17:11 Age [y:d:h:m:s]: 00:326:06:59:44
Block: 993479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233261 RingCT/type: yes/0
Extra: 01a99bee776cb27e360af087c22516ecaf7af325401efc7c650d3d2d9f870f4cb302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2ed3d892f942022442d8e2472f7380341fb52f24375efce911b87eb8c0a630 0.600000000000 1453865 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": 993489, "vin": [ { "gen": { "height": 993479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2ed3d892f942022442d8e2472f7380341fb52f24375efce911b87eb8c0a630" } } ], "extra": [ 1, 169, 155, 238, 119, 108, 178, 126, 54, 10, 240, 135, 194, 37, 22, 236, 175, 122, 243, 37, 64, 30, 252, 124, 101, 13, 61, 45, 159, 135, 15, 76, 179, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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