← previous blocknext block →recent activity
Analyzing
Block #87,920,746
30 transactions · 26 stateful · 2026-07-15 13:05:51 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,920,746 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w28w09w111w012w015w116w219w327w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca44ec…625f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x405da62e…192a
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc1a44382…f1ca
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x19cc9cff…c14c
0xd32edf…ff58
5 touches
3 conflicts
0x246db7bc…5a30
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x53ca44ecac…40625f
Audit this contract →
← previous block·next block →recent activity