Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c69094b333003f23e48e1f44f4dce5e7ddffff4989efe6f1c121a218138ddd7

Tx prefix hash: 0b3aed5e949ca56ed963000ff337a44f8af8210cf6a514603e92261a276380a7
Tx public key: deaea0661d903e2d91a3e3071bb8d56f2d0c944f4235b3bf9acb87ddbd79b17e
Timestamp: 1703985840 Timestamp [UCT]: 2023-12-31 01:24:00 Age [y:d:h:m:s]: 01:019:01:40:00
Block: 924778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274966 RingCT/type: yes/0
Extra: 01deaea0661d903e2d91a3e3071bb8d56f2d0c944f4235b3bf9acb87ddbd79b17e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82206661d5325895f36b5840eba7e197133946f5db4cbe972674b8760c3d9bee 0.600000000000 1382534 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": 924788, "vin": [ { "gen": { "height": 924778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82206661d5325895f36b5840eba7e197133946f5db4cbe972674b8760c3d9bee" } } ], "extra": [ 1, 222, 174, 160, 102, 29, 144, 62, 45, 145, 163, 227, 7, 27, 184, 213, 111, 45, 12, 148, 79, 66, 53, 179, 191, 154, 203, 135, 221, 189, 121, 177, 126, 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