Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69b287b99bca07d65995c426ccd1cff4b4b76ea8feaf3883e0220e9b18b1d023

Tx prefix hash: a9370d58e582b89d01b884c38b62de5b052dfbe974408c9bdb3c95953fc7cb36
Tx public key: eff391e1b692de3df228dbc3cc0b1d20a08bad9a76a1329db507316a1058e5a4
Timestamp: 1696680507 Timestamp [UCT]: 2023-10-07 12:08:27 Age [y:d:h:m:s]: 01:143:12:32:17
Block: 864424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363581 RingCT/type: yes/0
Extra: 01eff391e1b692de3df228dbc3cc0b1d20a08bad9a76a1329db507316a1058e5a4021100000003faf35c9c000000000000000000

1 output(s) for total of 0.839082153000 dcy

stealth address amount amount idx
00: 59618a3ddd3dd8a67175e6bb2d8afa228c9e7acd028fa4d3d8dcf30f96c87d8e 0.839082153000 1318938 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": 864434, "vin": [ { "gen": { "height": 864424 } } ], "vout": [ { "amount": 839082153, "target": { "key": "59618a3ddd3dd8a67175e6bb2d8afa228c9e7acd028fa4d3d8dcf30f96c87d8e" } } ], "extra": [ 1, 239, 243, 145, 225, 182, 146, 222, 61, 242, 40, 219, 195, 204, 11, 29, 32, 160, 139, 173, 154, 118, 161, 50, 157, 181, 7, 49, 106, 16, 88, 229, 164, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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