← previous blocknext block →recent activity
Analyzing
Block #87,639,523
17 transactions · 14 stateful · 2026-07-14 05:44:47 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,639,523 · 17 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
2w03w16w07w08w110w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2a49f3bf…713b
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1172247d…0022
0x34b655…2a6f
4 touches
1 conflict
0xc2872ff6…389b
0x34b655…2a6f
4 touches
1 conflict
0xe6b02948…7274
0x34b655…2a6f
4 touches
1 conflict
0xde696e46…6446
0x34b655…2a6f
4 touches
1 conflict
0x373ed4dc…49c9
0xd32edf…ff58
3 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