← previous blocknext block →recent activity
Analyzing
Block #87,697,551
17 transactions · 17 stateful · 2026-07-14 12:12:29 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,697,551 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w48w510w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02679875…8d2f
0x34b655…2a6f
10 touches
10 conflicts
0xc8f4deb0…dcf3
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x85c84f98…06d7
0x34b655…2a6f
6 touches
3 conflicts
0x15bb0662…b802
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbc96083d…124d
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0267987539…238d2f
Audit this contract →
← previous block·next block →recent activity