Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7799b9ba9da1838cff1d6341d90311421b1dc292f39cd0ca4502de67c6ef1d71

Tx prefix hash: 6b2dc777f633421ed04c984c78a527733569abb27a085f25e86fa12cb4252eac
Tx public key: 60c99aa68547e90df352d6f229a57df3d25c5f3245359a5d69d92086d760ef81
Timestamp: 1726336346 Timestamp [UCT]: 2024-09-14 17:52:26 Age [y:d:h:m:s]: 00:161:17:31:04
Block: 1110085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115378 RingCT/type: yes/0
Extra: 0160c99aa68547e90df352d6f229a57df3d25c5f3245359a5d69d92086d760ef81021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac57fb9dd097ba171d11f2ee66f9b486ba38b8c46e0254d97b88d8a742961f57 0.600000000000 1588566 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": 1110095, "vin": [ { "gen": { "height": 1110085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac57fb9dd097ba171d11f2ee66f9b486ba38b8c46e0254d97b88d8a742961f57" } } ], "extra": [ 1, 96, 201, 154, 166, 133, 71, 233, 13, 243, 82, 214, 242, 41, 165, 125, 243, 210, 92, 95, 50, 69, 53, 154, 93, 105, 217, 32, 134, 215, 96, 239, 129, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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