Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e965be7b5f881a6cbd4467d417706102279754eb46ddb4825f50b4773b5c53c0

Tx prefix hash: b37ab03f77a91996cc6282ee103e0b3dc9b01ddccd3bbebfade3887404903fc0
Tx public key: b9fa8c1a9f3c0938b9d4eee826ecf79d368e42eca2a6da99104ae484e509d53e
Timestamp: 1688680610 Timestamp [UCT]: 2023-07-06 21:56:50 Age [y:d:h:m:s]: 01:275:07:53:47
Block: 798162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457896 RingCT/type: yes/0
Extra: 01b9fa8c1a9f3c0938b9d4eee826ecf79d368e42eca2a6da99104ae484e509d53e02110000000575e3f0e9000000000000000000

1 output(s) for total of 1.391099177000 dcy

stealth address amount amount idx
00: 3bee7b52b227e9e89c56c65e34b068a72f97d9d0a4608c9401ba1e3f574cff23 1.391099177000 1249089 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": 798172, "vin": [ { "gen": { "height": 798162 } } ], "vout": [ { "amount": 1391099177, "target": { "key": "3bee7b52b227e9e89c56c65e34b068a72f97d9d0a4608c9401ba1e3f574cff23" } } ], "extra": [ 1, 185, 250, 140, 26, 159, 60, 9, 56, 185, 212, 238, 232, 38, 236, 247, 157, 54, 142, 66, 236, 162, 166, 218, 153, 16, 74, 228, 132, 229, 9, 213, 62, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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