← previous blocknext block →recent activity
Analyzing
Block #87,713,446
20 transactions · 18 stateful · 2026-07-14 13:59:04 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,713,446 · 20 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
1w02w13w04w05w16w27w311w312w413w414w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560ed681…07e6
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xcfaa395f…5b1c
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x48b8d2e5…3f2f
0x34b655…2a6f
4 touches
1 conflict
0x5cebb016…c149
0x34b655…2a6f
4 touches
1 conflict
0x6a1604d1…3e8a
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
6 conflicts on slot 0x560ed68159…1e07e6
Audit this contract →
← previous block·next block →recent activity