Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aead1f49cf276ca0d084a1c583bb53b9f67090190f8f60d30e06971cfd75114b

Tx prefix hash: 2da045d6a40732d20e7ea547da9677363db72bb3bbba8cdeb46ccae5d0ed32f4
Tx public key: 02f08cc2c0bd9804b0f93e5f99e543cc95da30e4743ef351a1d9c77a79ab1362
Timestamp: 1726049861 Timestamp [UCT]: 2024-09-11 10:17:41 Age [y:d:h:m:s]: 00:232:06:18:29
Block: 1107714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165847 RingCT/type: yes/0
Extra: 0102f08cc2c0bd9804b0f93e5f99e543cc95da30e4743ef351a1d9c77a79ab136202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e73ad83dc4e596c545d0f8b2f2d54f87c1ee7ee772cfce997efcf994e77b12da 0.600000000000 1585347 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": 1107724, "vin": [ { "gen": { "height": 1107714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e73ad83dc4e596c545d0f8b2f2d54f87c1ee7ee772cfce997efcf994e77b12da" } } ], "extra": [ 1, 2, 240, 140, 194, 192, 189, 152, 4, 176, 249, 62, 95, 153, 229, 67, 204, 149, 218, 48, 228, 116, 62, 243, 81, 161, 217, 199, 122, 121, 171, 19, 98, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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