← previous blocknext block →recent activity
Analyzing
Block #87,793,414
26 transactions · 22 stateful · 2026-07-14 22:54:12 UTC
Parallelism
69/100
Blocked
59%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,793,414 · 26 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
1w02w04w19w010w111w212w313w414w515w616w718w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
10 touches
10 conflicts
0xd8675136…9a01
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
10 touches
10 conflicts
0x9465204c…bf37
0x34b655…2a6f
10 touches
10 conflicts
0x28c62bca…b746
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
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