← previous blocknext block →recent activity
Analyzing
Block #96,277,768
22 transactions · 14 stateful · 2026-08-15 18:41:53 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,277,768 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w214w017w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49ffd065…33d1
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x71d38911…a353
0x065c9d…c394
3 touches
1 conflict
0xfce7a9c0…0766
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x49ffd065b3…cd33d1
Audit this contract →
← previous block·next block →recent activity