Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2005d485028ff916f962d43dbb4e6390051f313bf06ed1cbb254d25a74093747

Tx prefix hash: e5b0e7243117590284fe73a935f04dbb4ed831340297db875255e059db85ea90
Tx public key: e56a2ded8ac1cd0b0de866101e44753ec6dc541663f99d0eca8d22f7d9204347
Timestamp: 1712316433 Timestamp [UCT]: 2024-04-05 11:27:13 Age [y:d:h:m:s]: 01:041:17:49:23
Block: 993832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290832 RingCT/type: yes/0
Extra: 01e56a2ded8ac1cd0b0de866101e44753ec6dc541663f99d0eca8d22f7d92043470211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 244abc7f0293c80f1fdf0a2c584c7edd66750a313ffa2fb1554d8b3d4f4478b2 0.600000000000 1454220 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": 993842, "vin": [ { "gen": { "height": 993832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "244abc7f0293c80f1fdf0a2c584c7edd66750a313ffa2fb1554d8b3d4f4478b2" } } ], "extra": [ 1, 229, 106, 45, 237, 138, 193, 205, 11, 13, 232, 102, 16, 30, 68, 117, 62, 198, 220, 84, 22, 99, 249, 157, 14, 202, 141, 34, 247, 217, 32, 67, 71, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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