Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67c4c951e835f8e2953655b3480caf1ba2655ae81848c0602e3f7f5f74078220

Tx prefix hash: 4646378ebed38768aa90b804e056d8fa5d13a4b18ad661727d7879e8047a13c3
Tx public key: aa5c7bd68eced6fde2903bba7e9cf873a62a9bf0f74bf313b8ac6739a35f718c
Timestamp: 1731415151 Timestamp [UCT]: 2024-11-12 12:39:11 Age [y:d:h:m:s]: 00:142:13:07:26
Block: 1152100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101694 RingCT/type: yes/0
Extra: 01aa5c7bd68eced6fde2903bba7e9cf873a62a9bf0f74bf313b8ac6739a35f718c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b834456f55adf42e97c8409ade44d8e8445ed30467e5e947049e16d1fdd6ff08 0.600000000000 1637691 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": 1152110, "vin": [ { "gen": { "height": 1152100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b834456f55adf42e97c8409ade44d8e8445ed30467e5e947049e16d1fdd6ff08" } } ], "extra": [ 1, 170, 92, 123, 214, 142, 206, 214, 253, 226, 144, 59, 186, 126, 156, 248, 115, 166, 42, 155, 240, 247, 75, 243, 19, 184, 172, 103, 57, 163, 95, 113, 140, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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