← previous blocknext block →recent activity
Analyzing
Block #87,714,488
23 transactions · 21 stateful · 2026-07-14 14:06:06 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,714,488 · 23 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
1w02w13w26w07w112w013w215w316w418w419w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x709cb1f7…ed38
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0xd770071c…467d
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x113d8f93…5f36
0xd32edf…ff58
5 touches
3 conflicts
0x6d11d4a8…3a2d
0x34b655…2a6f
4 touches
1 conflict
0x86f32276…0ebf
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x709cb1f77e…faed38
Audit this contract →
← previous block·next block →recent activity