Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e0358f1bba8b2be1263339bed84fae243c9b4e41d75d4d6f38fa22234edb287

Tx prefix hash: 83e9984c567d12278aad94d129829c1fde8c98290076d216399f576f9ab8f92a
Tx public key: 215d7edc577481f79a87d2f9d73aea5c0ab61f97d469ec31c52f453440b33c6f
Timestamp: 1706001158 Timestamp [UCT]: 2024-01-23 09:12:38 Age [y:d:h:m:s]: 01:004:00:16:26
Block: 941470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264153 RingCT/type: yes/0
Extra: 01215d7edc577481f79a87d2f9d73aea5c0ab61f97d469ec31c52f453440b33c6f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01977536ff976de3c61e83861d8e7f2b3bb189cb342dea370627d2985a8a88b6 0.600000000000 1399620 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": 941480, "vin": [ { "gen": { "height": 941470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01977536ff976de3c61e83861d8e7f2b3bb189cb342dea370627d2985a8a88b6" } } ], "extra": [ 1, 33, 93, 126, 220, 87, 116, 129, 247, 154, 135, 210, 249, 215, 58, 234, 92, 10, 182, 31, 151, 212, 105, 236, 49, 197, 47, 69, 52, 64, 179, 60, 111, 2, 17, 0, 0, 0, 5, 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