← previous blocknext block →recent activity
Analyzing
Block #87,734,710
26 transactions · 26 stateful · 2026-07-14 16:21:29 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,734,710 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w112w013w114w215w316w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x2f461725…5ab2
0x34b655…2a6f
12 touches
15 conflicts
0xf71d302f…5814
0xd32edf…ff58
11 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc9564a5a…d74b
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x167de262…f61f
0x34b655…2a6f
10 touches
10 conflicts
0x58620f29…db5a
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity