Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e65bfba475ed49e0ea79614e1cd7ff841d5e45e137c4843c117a439ce6aaa4

Tx prefix hash: c00508f399452b5c3fec9785adfff3b4d274b8a0d0e706d6e1e7355dddbb2ec6
Tx public key: d073bfb1aa9f508173b1b44267bad6f7b361b1d9ba776df06f466f83931b6f1a
Timestamp: 1702208042 Timestamp [UCT]: 2023-12-10 11:34:02 Age [y:d:h:m:s]: 01:190:06:49:23
Block: 910057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397057 RingCT/type: yes/0
Extra: 01d073bfb1aa9f508173b1b44267bad6f7b361b1d9ba776df06f466f83931b6f1a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 468e2f608e906ab737601df6e910c98a73209f9fb39f80ac5adcd6c7745277e9 0.600000000000 1367198 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": 910067, "vin": [ { "gen": { "height": 910057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "468e2f608e906ab737601df6e910c98a73209f9fb39f80ac5adcd6c7745277e9" } } ], "extra": [ 1, 208, 115, 191, 177, 170, 159, 80, 129, 115, 177, 180, 66, 103, 186, 214, 247, 179, 97, 177, 217, 186, 119, 109, 240, 111, 70, 111, 131, 147, 27, 111, 26, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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