← previous blocknext block →recent activity
Analyzing
Block #96,639,165
22 transactions · 22 stateful · 2026-08-17 00:59:51 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,639,165 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w27w38w09w310w411w213w415w518w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6aef87…8137
0x34b655…2a6f
8 touches
6 conflicts
0x56153262…21ce
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x48532ab5…d4c1
0x34b655…2a6f
4 touches
1 conflict
0x48532ab5…d4c2
0x34b655…2a6f
4 touches
1 conflict
0x4c49ba5c…742e
0x34b655…2a6f
4 touches
1 conflict
0x69656781…3c53
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x0f6aef8771…dd8137
Audit this contract →
← previous block·next block →recent activity