Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735ee1fe0b6fa47d78e4a6b9420b7a1c9bde2f4f82d200994e1e19d06f056538

Tx prefix hash: 6a9173ebe392ca2836a57ee979783f5959bb71646a9aa07193e07f5b4b8c064b
Tx public key: 41284451986f81dbdca5edada87216ea1c32c0f8e5027badf29a66e475aded8c
Timestamp: 1672655441 Timestamp [UCT]: 2023-01-02 10:30:41 Age [y:d:h:m:s]: 02:309:06:12:49
Block: 665907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740422 RingCT/type: yes/0
Extra: 0141284451986f81dbdca5edada87216ea1c32c0f8e5027badf29a66e475aded8c02110000000252542ceb000000000000000000

1 output(s) for total of 3.815694896000 dcy

stealth address amount amount idx
00: 00aba3baeaebe1d6324ab611ff9f34d084f6498e12eff12e031a10b96f8ac20a 3.815694896000 1106976 of 0

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": 665917, "vin": [ { "gen": { "height": 665907 } } ], "vout": [ { "amount": 3815694896, "target": { "key": "00aba3baeaebe1d6324ab611ff9f34d084f6498e12eff12e031a10b96f8ac20a" } } ], "extra": [ 1, 65, 40, 68, 81, 152, 111, 129, 219, 220, 165, 237, 173, 168, 114, 22, 234, 28, 50, 192, 248, 229, 2, 123, 173, 242, 154, 102, 228, 117, 173, 237, 140, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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