← previous blocknext block →recent activity
Analyzing
Block #86,988,888
22 transactions · 21 stateful · 2026-07-11 05:13:22 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,988,888 · 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
3w04w17w29w312w313w416w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x31c77e11…2fd8
0x34b655…2a6f
6 touches
3 conflicts
0x008accc4…1da7
0x34b655…2a6f
6 touches
3 conflicts
0x1363d531…a90a
0x34b655…2a6f
6 touches
3 conflicts
0x7ae44958…8593
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810d
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity