Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2d934491c7959ce079669ffef653653a1401236dc7f6525a693afb7a8f5d25e

Tx prefix hash: 9b18f9da5638f0eb970c718cd7bebe872863b1d670357529c871f1db21b4d61a
Tx public key: 060f3919b4f66c0f5b4035ecf76b24983ae79c066eac241334da8186f6878c84
Timestamp: 1733874162 Timestamp [UCT]: 2024-12-10 23:42:42 Age [y:d:h:m:s]: 00:099:23:29:30
Block: 1172481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71259 RingCT/type: yes/0
Extra: 01060f3919b4f66c0f5b4035ecf76b24983ae79c066eac241334da8186f6878c84021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4de8fe36efb729b687ad12ae8d44c9b8accdd69d1309ee3100a46377dda99d8e 0.600000000000 1658378 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": 1172491, "vin": [ { "gen": { "height": 1172481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4de8fe36efb729b687ad12ae8d44c9b8accdd69d1309ee3100a46377dda99d8e" } } ], "extra": [ 1, 6, 15, 57, 25, 180, 246, 108, 15, 91, 64, 53, 236, 247, 107, 36, 152, 58, 231, 156, 6, 110, 172, 36, 19, 52, 218, 129, 134, 246, 135, 140, 132, 2, 17, 0, 0, 0, 2, 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