← previous blocknext block →recent activity
Analyzing
Block #88,194,131
16 transactions · 15 stateful · 2026-07-16 19:35:20 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,194,131 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w09w110w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b580bf…f969
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2bad40ae…0523
0x34b655…2a6f
4 touches
1 conflict
0xc994d804…2fca
0x34b655…2a6f
4 touches
1 conflict
0xc994d804…2fcb
0x34b655…2a6f
4 touches
1 conflict
0xedf27b30…9b7b
0x34b655…2a6f
4 touches
1 conflict
0x43c943e1…8f47
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
3 conflicts on slot 0x56b580bf44…22f969
Audit this contract →
← previous block·next block →recent activity