← previous blocknext block →recent activity
Analyzing
Block #88,137,353
8 transactions · 7 stateful · 2026-07-16 13:14:42 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,137,353 · 8 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
2w03w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x313a4aca…e2f5
0x34b655…2a6f
2 touches
0 conflicts
0x47a10383…3e35
0x34b655…2a6f
2 touches
0 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x62030a81…91be
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity