Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a863827d5c5b9c1c65d1ce36cf2c6457752a694e13ac77b1ef82e2a5940d51c6

Tx prefix hash: e3a1617cf1d41e4bf5e392ebd35b594d2cf20f01bf444a4c12e835475c947700
Tx public key: 8e89d2c9004743f9f68362d51c0c42d08282ed4c02edc5b079f4e45c918d8780
Timestamp: 1687425738 Timestamp [UCT]: 2023-06-22 09:22:18 Age [y:d:h:m:s]: 01:323:10:14:00
Block: 787745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492337 RingCT/type: yes/0
Extra: 018e89d2c9004743f9f68362d51c0c42d08282ed4c02edc5b079f4e45c918d8780021100000003faf35c9c000000000000000000

1 output(s) for total of 1.506169866000 dcy

stealth address amount amount idx
00: 27e0c91b2b2ac97f444eeaf4776f5b1df5f27447bf4d55ff2a618b6f0cfb3439 1.506169866000 1237824 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": 787755, "vin": [ { "gen": { "height": 787745 } } ], "vout": [ { "amount": 1506169866, "target": { "key": "27e0c91b2b2ac97f444eeaf4776f5b1df5f27447bf4d55ff2a618b6f0cfb3439" } } ], "extra": [ 1, 142, 137, 210, 201, 0, 71, 67, 249, 246, 131, 98, 213, 28, 12, 66, 208, 130, 130, 237, 76, 2, 237, 197, 176, 121, 244, 228, 92, 145, 141, 135, 128, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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