Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d194030e97b0ee1530d7b82d2ba845116082259ae5cadbe7f8fa9c7601dfafd

Tx prefix hash: 78e73f747929df13ea47ff99dd180a50b312a6b5ae6cbd74eb235b258437cb99
Tx public key: 51bfef427fe5dda7049fd569c7bd62fdf5d9bf48986cba4b93703a275d8c99ba
Timestamp: 1707274768 Timestamp [UCT]: 2024-02-07 02:59:28 Age [y:d:h:m:s]: 00:343:20:55:51
Block: 952050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246172 RingCT/type: yes/0
Extra: 0151bfef427fe5dda7049fd569c7bd62fdf5d9bf48986cba4b93703a275d8c99ba0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3587f8437bae60e4cf3e4bf863ba63637ce40cee2a9358cecf3b251dac7bbc61 0.600000000000 1410922 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": 952060, "vin": [ { "gen": { "height": 952050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3587f8437bae60e4cf3e4bf863ba63637ce40cee2a9358cecf3b251dac7bbc61" } } ], "extra": [ 1, 81, 191, 239, 66, 127, 229, 221, 167, 4, 159, 213, 105, 199, 189, 98, 253, 245, 217, 191, 72, 152, 108, 186, 75, 147, 112, 58, 39, 93, 140, 153, 186, 2, 17, 0, 0, 0, 4, 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