Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d988aad94f4099cc504c5de3a051c0da31fbd1ce81921c758517e53065137e6e

Tx prefix hash: fc2fcdf5d2061db212cb283510539300e4712e417d630e67a81d61ea3943d120
Tx public key: 7571f1e9922511f044f0f8c82db888a4fb3dd90e3680abd63827e3dedb7060f3
Timestamp: 1676255495 Timestamp [UCT]: 2023-02-13 02:31:35 Age [y:d:h:m:s]: 02:265:07:34:49
Block: 695785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708926 RingCT/type: yes/0
Extra: 017571f1e9922511f044f0f8c82db888a4fb3dd90e3680abd63827e3dedb7060f3021100000002e7ace25d000000000000000000

1 output(s) for total of 3.037913336000 dcy

stealth address amount amount idx
00: f05ab726847e1c432ec692aff1fa57323d656c7181aa2d74c3879d52247b5aea 3.037913336000 1138744 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": 695795, "vin": [ { "gen": { "height": 695785 } } ], "vout": [ { "amount": 3037913336, "target": { "key": "f05ab726847e1c432ec692aff1fa57323d656c7181aa2d74c3879d52247b5aea" } } ], "extra": [ 1, 117, 113, 241, 233, 146, 37, 17, 240, 68, 240, 248, 200, 45, 184, 136, 164, 251, 61, 217, 14, 54, 128, 171, 214, 56, 39, 227, 222, 219, 112, 96, 243, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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