← previous blocknext block →recent activity
Analyzing
Block #87,498,405
35 transactions · 31 stateful · 2026-07-13 14:00:13 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,498,405 · 35 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
2w04w18w09w110w011w212w313w414w517w118w319w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x8cf1f868…c5af
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x369883e3…a449
0x34b655…2a6f
8 touches
6 conflicts
0xe20a9313…c20a
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x737acb78…fce8
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