← previous blocknext block →recent activity
Analyzing
Block #87,417,835
16 transactions · 16 stateful · 2026-07-13 05:01:30 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,417,835 · 16 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
1w02w04w15w26w27w18w312w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf69bf8bb…421f
0x34b655…2a6f
6 touches
3 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0x40287836…2dff
0x34b655…2a6f
4 touches
1 conflict
0x563bbb55…861a
0x34b655…2a6f
4 touches
1 conflict
0x60ba1280…cd6c
0x34b655…2a6f
4 touches
1 conflict
0x61757a59…d89f
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity