← previous blocknext block →recent activity
Analyzing
Block #88,090,704
12 transactions · 11 stateful · 2026-07-16 08:02:36 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,090,704 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x0a049021…fd96
0x34b655…2a6f
4 touches
1 conflict
0xa9ff3219…65d6
0x34b655…2a6f
4 touches
1 conflict
0xc8559aff…8257
0x34b655…2a6f
4 touches
1 conflict
0x0a049021…fd97
0x34b655…2a6f
4 touches
1 conflict
0x4dc5de9e…bcec
0x34b655…2a6f
3 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2acd406f…1f22
0x34b655…2a6f
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 0x6762cac28d…f93fb0
Audit this contract →
← previous block·next block →recent activity