← previous blocknext block →recent activity
Analyzing
Block #87,063,741
9 transactions · 7 stateful · 2026-07-11 13:33:29 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,063,741 · 9 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
1w02w13w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x710f9ad0…7e63
0x34b655…2a6f
6 touches
3 conflicts
0xfdbc4c4c…0cf3
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8cc1393f…07fb
0x34b655…2a6f
4 touches
1 conflict
0x8eedf936…a0c3
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity