Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5df4263493fd01f53b77fd97cb22ddd86e9bb96fff4c1314c7a5dc7893a20ce

Tx prefix hash: a72c3a8fe18c6af34cef243d25920578b5bb7d9f6ccce736e13383bc87a66288
Tx public key: 440e912b97ad771424d539a30103d06e0a5fb0308da9d812e53b7fa84523a1c7
Timestamp: 1732963384 Timestamp [UCT]: 2024-11-30 10:43:04 Age [y:d:h:m:s]: 00:127:07:05:38
Block: 1164926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90776 RingCT/type: yes/0
Extra: 01440e912b97ad771424d539a30103d06e0a5fb0308da9d812e53b7fa84523a1c7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66d1ba73638e725ef56041ca9ad2c87c9e5e61098239831af02fdd3b6123e1cd 0.600000000000 1650601 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": 1164936, "vin": [ { "gen": { "height": 1164926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66d1ba73638e725ef56041ca9ad2c87c9e5e61098239831af02fdd3b6123e1cd" } } ], "extra": [ 1, 68, 14, 145, 43, 151, 173, 119, 20, 36, 213, 57, 163, 1, 3, 208, 110, 10, 95, 176, 48, 141, 169, 216, 18, 229, 59, 127, 168, 69, 35, 161, 199, 2, 17, 0, 0, 0, 3, 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