← previous blocknext block →recent activity
Analyzing
Block #88,184,229
18 transactions · 17 stateful · 2026-07-16 18:28:54 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,184,229 · 18 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
6w08w09w110w111w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d158563…8713
0x34b655…2a6f
6 touches
3 conflicts
0xb4b1158e…aaef
0x34b655…2a6f
4 touches
1 conflict
0xc2ebcc0c…2261
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x06c980ab…5577
0x34b655…2a6f
4 touches
1 conflict
0x16dce2e7…6f05
0x34b655…2a6f
4 touches
1 conflict
0x1c48b3ac…a03c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x3d1585630c…178713
Audit this contract →
← previous block·next block →recent activity