Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b363ab595dc6a8fe35feb86beaa6de545778e0bb7cd3cecc40a1dfdbbe7c8fe6

Tx prefix hash: 002cb0eda635bc796fa6cdc88f295308e3b13a367d35e2d9b84ee0316744331d
Tx public key: 449bc8c8c5ac5674a59a862a724b74cb777cf65d0be6d6ded3faa28c2d792c49
Timestamp: 1720085416 Timestamp [UCT]: 2024-07-04 09:30:16 Age [y:d:h:m:s]: 00:267:03:58:09
Block: 1058263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190884 RingCT/type: yes/0
Extra: 01449bc8c8c5ac5674a59a862a724b74cb777cf65d0be6d6ded3faa28c2d792c4902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c88d7e09a0e91bdba8540ede925260d21853096ab0f5448717476e8044a8b5d4 0.600000000000 1528712 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": 1058273, "vin": [ { "gen": { "height": 1058263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c88d7e09a0e91bdba8540ede925260d21853096ab0f5448717476e8044a8b5d4" } } ], "extra": [ 1, 68, 155, 200, 200, 197, 172, 86, 116, 165, 154, 134, 42, 114, 75, 116, 203, 119, 124, 246, 93, 11, 230, 214, 222, 211, 250, 162, 140, 45, 121, 44, 73, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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