Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bd2dd84a3fe01dc5663b350601c9c833e3b08b19d6a17da4e13fcfbdc3131d3

Tx prefix hash: 778aa105bcc9f71614079ed81c28e7d467dcf425a886408cb1332b950bfd1fbc
Tx public key: d54fe2e73ea554afc6e07a936934bfb1c1c66ab1727f489e31255122bbdf08ba
Timestamp: 1719248843 Timestamp [UCT]: 2024-06-24 17:07:23 Age [y:d:h:m:s]: 01:106:09:43:20
Block: 1051306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334571 RingCT/type: yes/0
Extra: 01d54fe2e73ea554afc6e07a936934bfb1c1c66ab1727f489e31255122bbdf08ba02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc849fde00e97a37691e572e489c1fb4e321f0c2154ce3f420699a36b717eebd 0.600000000000 1521615 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": 1051316, "vin": [ { "gen": { "height": 1051306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc849fde00e97a37691e572e489c1fb4e321f0c2154ce3f420699a36b717eebd" } } ], "extra": [ 1, 213, 79, 226, 231, 62, 165, 84, 175, 198, 224, 122, 147, 105, 52, 191, 177, 193, 198, 106, 177, 114, 127, 72, 158, 49, 37, 81, 34, 187, 223, 8, 186, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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