← previous blocknext block →recent activity
Analyzing
Block #87,715,152
22 transactions · 19 stateful · 2026-07-14 14:10:32 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,715,152 · 22 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
1w02w14w05w16w28w19w214w315w416w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb529f62…663c
0x34b655…2a6f
12 touches
15 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
10 touches
10 conflicts
0x42dd9d36…3fc0
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x239122db…dc81
0x34b655…2a6f
6 touches
3 conflicts
0xaa2a27f2…d53b
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x92385428…6941
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
15 conflicts on slot 0xdb529f62fb…23663c
Audit this contract →
← previous block·next block →recent activity