← previous blocknext block →recent activity
Analyzing
Block #87,754,716
22 transactions · 21 stateful · 2026-07-14 18:35:19 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,754,716 · 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
1w06w07w18w29w310w413w114w515w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x26acd5b4…4f06
0x34b655…2a6f
6 touches
3 conflicts
0x28c62bca…b746
0x34b655…2a6f
6 touches
3 conflicts
0x5e3a31d1…7a6e
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity