← previous blocknext block →recent activity
Analyzing
Block #87,063,309
9 transactions · 8 stateful · 2026-07-11 13:30:36 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,063,309 · 9 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x4b2b1640…1bb8
0x34b655…2a6f
4 touches
1 conflict
0x0285a6d7…8f1a
0x34b655…2a6f
2 touches
0 conflicts
0x0c002dd1…af10
0x34b655…2a6f
2 touches
0 conflicts
0x0c326f2b…8e5a
0x34b655…2a6f
2 touches
0 conflicts
0x22af2e4e…609c
0x34b655…2a6f
2 touches
0 conflicts
0x56b5f5c0…a3ad
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity