← previous blocknext block →recent activity
Analyzing
Block #87,715,984
20 transactions · 17 stateful · 2026-07-14 14:16:09 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,715,984 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w010w111w212w315w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf726e2e2…e561
0x34b655…2a6f
6 touches
3 conflicts
0xdd36917c…b88b
0x34b655…2a6f
6 touches
3 conflicts
0x7eb90864…574d
0x34b655…2a6f
4 touches
1 conflict
0x7f49daa2…3ac1
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
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
10 conflicts on slot 0x93b6fab01a…2d09d6
Audit this contract →
← previous block·next block →recent activity