Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69753fe8a12edbfd086bb66fb1da4efa19a9367544d9cdbf32ea63801af5be9a

Tx prefix hash: b6fee36adcc56210f318ad36d4844b5c924c1194e7e4f27a7d41873800974e84
Tx public key: 306f87ab1edb9b92b4df1ffcc4601f90a1010bf979e0f4ee402a363b6db3611b
Timestamp: 1708703422 Timestamp [UCT]: 2024-02-23 15:50:22 Age [y:d:h:m:s]: 00:334:23:41:48
Block: 963906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239755 RingCT/type: yes/0
Extra: 01306f87ab1edb9b92b4df1ffcc4601f90a1010bf979e0f4ee402a363b6db3611b02110000001459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 171578b17352927db991353ac032a861adfffa73950bdab6e46b0f2d16a2d941 0.600000000000 1423633 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": 963916, "vin": [ { "gen": { "height": 963906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171578b17352927db991353ac032a861adfffa73950bdab6e46b0f2d16a2d941" } } ], "extra": [ 1, 48, 111, 135, 171, 30, 219, 155, 146, 180, 223, 31, 252, 196, 96, 31, 144, 161, 1, 11, 249, 121, 224, 244, 238, 64, 42, 54, 59, 109, 179, 97, 27, 2, 17, 0, 0, 0, 20, 89, 218, 211, 245, 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