← previous blocknext block →recent activity
Analyzing
Block #87,419,782
13 transactions · 12 stateful · 2026-07-13 05:14:30 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,419,782 · 13 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
1w02w13w24w35w08w19w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67d8b378…f2f8
0x34b655…2a6f
8 touches
6 conflicts
0x16b3a441…13db
0x34b655…2a6f
6 touches
3 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x43738f23…b864
0x34b655…2a6f
6 touches
3 conflicts
0x5b353877…605d
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
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 0x67d8b378d2…4df2f8
Audit this contract →
← previous block·next block →recent activity