← previous blocknext block →recent activity
Analyzing
Block #87,616,690
17 transactions · 14 stateful · 2026-07-14 03:12:06 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,616,690 · 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
1w02w14w05w16w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe60e9000…c058
0x34b655…2a6f
6 touches
3 conflicts
0xf4ca4a80…b15d
0x34b655…2a6f
6 touches
3 conflicts
0x3e0072a8…95fc
0x34b655…2a6f
4 touches
1 conflict
0x4e3e1251…e95d
0x34b655…2a6f
4 touches
1 conflict
0xf7af8195…cea4
0x34b655…2a6f
4 touches
1 conflict
0xb176789b…c34b
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity