← previous blocknext block →recent activity
Analyzing
Block #87,696,311
24 transactions · 21 stateful · 2026-07-14 12:04:11 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,696,311 · 24 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
1w02w14w07w08w19w211w212w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x864353d4…dcb7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xf386bff1…b350
0x34b655…2a6f
4 touches
1 conflict
0xe2307994…acad
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x24f6d4ca…c33b
0x34b655…2a6f
4 touches
1 conflict
0x4e3abeff…18eb
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity