← previous blocknext block →recent activity
Analyzing
Block #87,626,548
15 transactions · 14 stateful · 2026-07-14 04:18:00 UTC
Parallelism
73/100
Blocked
64%
Avg conflicts / tx
1.07
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,626,548 · 15 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
1w03w04w15w26w37w18w29w111w312w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3f008b3…b7c9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x3c4b8fbd…9354
0x34b655…2a6f
6 touches
3 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0xa24365bc…5064
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb3f008b3b9…6ab7c9
Audit this contract →
← previous block·next block →recent activity