← previous blocknext block →recent activity
Analyzing
Block #87,713,731
19 transactions · 16 stateful · 2026-07-14 14:01:00 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,713,731 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w49w512w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x333c820d…10c1
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x9eb155db…f714
0x34b655…2a6f
6 touches
3 conflicts
0xa9988d79…09ff
0x34b655…2a6f
6 touches
3 conflicts
0x5ec64628…72e4
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
10 conflicts on slot 0x333c820d6f…7d10c1
Audit this contract →
← previous block·next block →recent activity