← previous blocknext block →recent activity
Analyzing
Block #96,024,639
20 transactions · 18 stateful · 2026-08-14 21:28:40 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,024,639 · 20 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
3w06w07w19w210w311w012w214w115w416w218w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9719e4fc…0cda
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0xd08d1657…e444
0x34b655…2a6f
4 touches
1 conflict
0x48b58394…2894
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
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 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity