← previous blocknext block →recent activity
Analyzing
Block #87,050,014
13 transactions · 13 stateful · 2026-07-11 12:01:51 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,050,014 · 13 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
1w03w16w07w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee06e767…00d6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0x2fead171…13d6
0x34b655…2a6f
4 touches
1 conflict
0x453f53a8…e541
0x34b655…2a6f
4 touches
1 conflict
0x58f65aa1…8f98
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
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 0xee06e76704…0e00d6
Audit this contract →
← previous block·next block →recent activity