← previous blocknext block →recent activity
Analyzing
Block #87,729,362
36 transactions · 30 stateful · 2026-07-14 15:45:43 UTC
Parallelism
86/100
Blocked
57%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,729,362 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w15w28w29w311w012w113w214w315w427w429w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0004
0x63e48b…53f2
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
10 touches
10 conflicts
0x6f9b16e8…b75f
0xd32edf…ff58
9 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
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: 0x63e48b72…8c53f2
10 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity