← previous blocknext block →recent activity
Analyzing
Block #87,715,175
50 transactions · 39 stateful · 2026-07-14 14:10:41 UTC
Parallelism
80/100
Blocked
64%
Avg conflicts / tx
1.86
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,715,175 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w08w19w210w311w412w513w641w343w245w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0x04fdea…47d7
14 touches
21 conflicts
0xa6389d47…9a28
0x34b655…2a6f
10 touches
10 conflicts
0x966e45cf…0f25
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity