← previous blocknext block →recent activity
Analyzing
Block #88,040,271
12 transactions · 10 stateful · 2026-07-16 02:25:19 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,040,271 · 12 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
1w06w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50e84e6c…287f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0132a858…c59e
0x851145…3f07
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x87bdb64a…593a
0x34b655…2a6f
4 touches
1 conflict
0xb76f7c01…c3a5
0x34b655…2a6f
4 touches
1 conflict
0xcc13c07b…d7cc
0x34b655…2a6f
4 touches
1 conflict
0xd209b98e…8018
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 0x50e84e6ca8…2d287f
Audit this contract →
← previous block·next block →recent activity