← previous blocknext block →recent activity
Analyzing
Block #87,130,874
17 transactions · 16 stateful · 2026-07-11 21:01:50 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,130,874 · 17 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
7w08w09w111w212w313w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x8267cc91…78bc
0x34b655…2a6f
8 touches
6 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0x3a1edb3e…b841
0x34b655…2a6f
4 touches
1 conflict
0x4b2b1640…1bb8
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity