← previous blocknext block →recent activity
Analyzing
Block #88,365,184
22 transactions · 20 stateful · 2026-07-17 14:39:47 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,365,184 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w111w112w213w014w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e166a45…98a7
0x34b655…2a6f
6 touches
3 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
6 touches
3 conflicts
0xd3d2b624…594f
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x53ca44ec…625f
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 0x1e166a4530…8298a7
Audit this contract →
← previous block·next block →recent activity