← previous blocknext block →recent activity
Analyzing
Block #88,076,186
17 transactions · 16 stateful · 2026-07-16 06:25:30 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,076,186 · 17 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
3w06w07w18w19w210w213w014w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd34b5587…cc86
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9c
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d2f2e75…e6b6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xd34b558714…30cc86
Audit this contract →
← previous block·next block →recent activity