← previous blocknext block →recent activity
Analyzing
Block #87,714,631
32 transactions · 30 stateful · 2026-07-14 14:07:03 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,714,631 · 32 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
1w02w13w24w05w16w07w18w010w111w112w213w314w415w518w219w320w624w727w228w231w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xa6389d47…9a28
0x34b655…2a6f
10 touches
10 conflicts
0x9354a4d0…be91
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
8 touches
6 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x64098913…b17c
0x34b655…2a6f
8 touches
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity