Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff4ddc3a747af18b89a13978c409b3e46f6c2e2fc8c986636b4cdcb08398fe83

Tx prefix hash: 625e4c3c9b55bd8d439a21978e7c2b64ade15b92d3e04399cf4a98ac04a94ef9
Tx public key: 15bf1bcec11e26e2cbc834c66f634910ae0888fc67a0cb08111c0c842b622458
Timestamp: 1694096383 Timestamp [UCT]: 2023-09-07 14:19:43 Age [y:d:h:m:s]: 01:234:06:56:17
Block: 842989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428570 RingCT/type: yes/0
Extra: 0115bf1bcec11e26e2cbc834c66f634910ae0888fc67a0cb08111c0c842b622458021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.988160679000 dcy

stealth address amount amount idx
00: c34f6d7e6991c22b23be99fbaacd722363cd7bcad600a28bdeec6d2614845996 0.988160679000 1296171 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": 842999, "vin": [ { "gen": { "height": 842989 } } ], "vout": [ { "amount": 988160679, "target": { "key": "c34f6d7e6991c22b23be99fbaacd722363cd7bcad600a28bdeec6d2614845996" } } ], "extra": [ 1, 21, 191, 27, 206, 193, 30, 38, 226, 203, 200, 52, 198, 111, 99, 73, 16, 174, 8, 136, 252, 103, 160, 203, 8, 17, 28, 12, 132, 43, 98, 36, 88, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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