Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adfdf98d8e130c96abcb602253879b34fd4ca47726168f8920d467e9020dc65d

Tx prefix hash: b8bdd587bb59e845bc6c6c876c59a2bc36f4caac091629e11fbeeded51798553
Tx public key: 2d69a9fbd66fbe87db90e8c358e3ed9e56835147c14f5941b2f2ed09e9e169f7
Timestamp: 1712363138 Timestamp [UCT]: 2024-04-06 00:25:38 Age [y:d:h:m:s]: 01:274:23:52:44
Block: 994206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455342 RingCT/type: yes/0
Extra: 012d69a9fbd66fbe87db90e8c358e3ed9e56835147c14f5941b2f2ed09e9e169f702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e6a021adab9ad6e54b6cd178094d1ce9e6faf58ead0f035a2d01ad40351e75d 0.600000000000 1454608 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": 994216, "vin": [ { "gen": { "height": 994206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e6a021adab9ad6e54b6cd178094d1ce9e6faf58ead0f035a2d01ad40351e75d" } } ], "extra": [ 1, 45, 105, 169, 251, 214, 111, 190, 135, 219, 144, 232, 195, 88, 227, 237, 158, 86, 131, 81, 71, 193, 79, 89, 65, 178, 242, 237, 9, 233, 225, 105, 247, 2, 17, 0, 0, 0, 1, 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