Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a8bf3c558587526616b6c8056686d2e46be147de79ba149b95ee79d829de40

Tx prefix hash: 165d3dba904001ac3e3adf67da9578b8359ca39d7c896b6de378e6f9b4657c40
Tx public key: 0b489862c3a3cd608c9caa1727afd0c233f6d932aecfc80cb0668e234aa612c5
Timestamp: 1710231607 Timestamp [UCT]: 2024-03-12 08:20:07 Age [y:d:h:m:s]: 01:265:23:04:42
Block: 976588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448810 RingCT/type: yes/0
Extra: 010b489862c3a3cd608c9caa1727afd0c233f6d932aecfc80cb0668e234aa612c50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6060e766ee59173823a65dfd69e94cfbf7fefc4505be9b8cebe0f110082cd7 0.600000000000 1436583 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": 976598, "vin": [ { "gen": { "height": 976588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6060e766ee59173823a65dfd69e94cfbf7fefc4505be9b8cebe0f110082cd7" } } ], "extra": [ 1, 11, 72, 152, 98, 195, 163, 205, 96, 140, 156, 170, 23, 39, 175, 208, 194, 51, 246, 217, 50, 174, 207, 200, 12, 176, 102, 142, 35, 74, 166, 18, 197, 2, 17, 0, 0, 0, 3, 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