← previous blocknext block →recent activity
Analyzing
Block #87,265,209
9 transactions · 8 stateful · 2026-07-12 12:00:45 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,265,209 · 9 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
2w03w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd850e8c6…62f8
0x34b655…2a6f
6 touches
3 conflicts
0xea297ef6…552e
0x34b655…2a6f
4 touches
1 conflict
0x365bd58a…0eb5
0x34b655…2a6f
4 touches
1 conflict
0x4ed9c6f1…c867
0x34b655…2a6f
4 touches
1 conflict
0x6f761690…95bd
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity