← previous blocknext block →recent activity
Analyzing
Block #87,594,724
37 transactions · 32 stateful · 2026-07-14 00:45:12 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
1.73
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,594,724 · 37 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w09w110w011w012w213w314w415w516w617w719w120w621w122w724w825w927w128w232w833w934w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x83b16bf0…4083
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0x3cb8c8c3…22f4
0x34b655…2a6f
6 touches
3 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
6 touches
3 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
6 touches
3 conflicts
0xb6abb885…ce9c
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity