Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a93c929082e5ac2d70cfede53aa2184db156922745bf48ae30a07184182064

Tx prefix hash: 172642ba9d698ebf24571b5e18251c7d020d037e486b1e56a0b114872aec8fe3
Tx public key: 2b557a891acf6d807ead091fac8ae8c302a21f126e05eb59a382e0ece25f448b
Timestamp: 1711935374 Timestamp [UCT]: 2024-04-01 01:36:14 Age [y:d:h:m:s]: 01:045:22:31:47
Block: 990711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293799 RingCT/type: yes/0
Extra: 012b557a891acf6d807ead091fac8ae8c302a21f126e05eb59a382e0ece25f448b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9b3d966d5edaa64b4f8f59be44d648131238af62507aad113e9a90bf16cb1c 0.600000000000 1451037 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": 990721, "vin": [ { "gen": { "height": 990711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9b3d966d5edaa64b4f8f59be44d648131238af62507aad113e9a90bf16cb1c" } } ], "extra": [ 1, 43, 85, 122, 137, 26, 207, 109, 128, 126, 173, 9, 31, 172, 138, 232, 195, 2, 162, 31, 18, 110, 5, 235, 89, 163, 130, 224, 236, 226, 95, 68, 139, 2, 17, 0, 0, 0, 1, 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