Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61224604bb1051d27773e5d6870f473d3cd0bcc53396d688b008d1c84e7d413

Tx prefix hash: c785e7b6e47198c635e1d69397c5ef4d1482d261b9bde43d42d35ead5350be5d
Tx public key: e85a21820b007cc6e7ecb7db24a32ec915cc5c3fbaf8719ff0eb03eeb1b449e7
Timestamp: 1737967716 Timestamp [UCT]: 2025-01-27 08:48:36 Age [y:d:h:m:s]: 00:046:03:49:33
Block: 1206128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33004 RingCT/type: yes/0
Extra: 01e85a21820b007cc6e7ecb7db24a32ec915cc5c3fbaf8719ff0eb03eeb1b449e70211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb16c118a0082fc671dbd45f73f7191547e8947bdf75913206bb29530f8368c8 0.600000000000 1692831 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": 1206138, "vin": [ { "gen": { "height": 1206128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb16c118a0082fc671dbd45f73f7191547e8947bdf75913206bb29530f8368c8" } } ], "extra": [ 1, 232, 90, 33, 130, 11, 0, 124, 198, 231, 236, 183, 219, 36, 163, 46, 201, 21, 204, 92, 63, 186, 248, 113, 159, 240, 235, 3, 238, 177, 180, 73, 231, 2, 17, 0, 0, 0, 6, 31, 10, 83, 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