Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d5832658d2e874aa03b723b18e0fe5ec9981e756030f6ccacc7144ec62b16e

Tx prefix hash: 8497c4fdb6dc29949766d7cc1175eb5e28aac4af11eb2495a313048196c06244
Tx public key: 9f3e6c8e8971a303ec5206216ea587853b8b695d157133e4968edb39e8569bc8
Timestamp: 1700760760 Timestamp [UCT]: 2023-11-23 17:32:40 Age [y:d:h:m:s]: 01:177:04:52:42
Block: 898054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387834 RingCT/type: yes/0
Extra: 019f3e6c8e8971a303ec5206216ea587853b8b695d157133e4968edb39e8569bc802110000000675e3f0e9000000000000000000

1 output(s) for total of 0.649193682000 dcy

stealth address amount amount idx
00: b26a05b4eadd89f8c1cd3306ae21669abcbdfb91233bb729aaa0e00f2d60f5f9 0.649193682000 1354457 of 0

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": 898064, "vin": [ { "gen": { "height": 898054 } } ], "vout": [ { "amount": 649193682, "target": { "key": "b26a05b4eadd89f8c1cd3306ae21669abcbdfb91233bb729aaa0e00f2d60f5f9" } } ], "extra": [ 1, 159, 62, 108, 142, 137, 113, 163, 3, 236, 82, 6, 33, 110, 165, 135, 133, 59, 139, 105, 93, 21, 113, 51, 228, 150, 142, 219, 57, 232, 86, 155, 200, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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