← previous blocknext block →recent activity
Analyzing
Block #87,576,649
14 transactions · 11 stateful · 2026-07-13 22:44:19 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,576,649 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x822bd4f1…6b3a
0x34b655…2a6f
4 touches
1 conflict
0x0933b65e…e7d4
0x34b655…2a6f
2 touches
0 conflicts
0x156a190c…4085
0x34b655…2a6f
2 touches
0 conflicts
0x17fbe072…2ea6
0x34b655…2a6f
2 touches
0 conflicts
0x1a5d321d…a474
0x34b655…2a6f
2 touches
0 conflicts
0x26bcd08c…8b42
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity