← previous blocknext block →recent activity
Analyzing
Block #87,715,042
10 transactions · 8 stateful · 2026-07-14 14:09:48 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,715,042 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e7b3b3…a0e4
0x34b655…2a6f
4 touches
1 conflict
0xc3d5ea28…4118
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9354a4d0…be91
0x34b655…2a6f
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x0d55d89d…a4ec
0x34b655…2a6f
2 touches
0 conflicts
0x270fa94a…95a6
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
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 0xb4e7b3b399…b8a0e4
Audit this contract →
← previous block·next block →recent activity