← previous blocknext block →recent activity
Analyzing
Block #87,688,637
11 transactions · 11 stateful · 2026-07-14 11:12:56 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,688,637 · 11 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
1w02w13w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e3abeff…18eb
0x34b655…2a6f
8 touches
6 conflicts
0x96d4f560…c558
0x34b655…2a6f
4 touches
1 conflict
0xd0243b19…507b
0x34b655…2a6f
4 touches
1 conflict
0xf0feb15e…420b
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2879
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
6 conflicts on slot 0x4e3abefffa…8618eb
Audit this contract →
← previous block·next block →recent activity