← previous blocknext block →recent activity
Analyzing
Block #87,730,507
16 transactions · 14 stateful · 2026-07-14 15:53:22 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,730,507 · 16 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
4w05w111w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8f29aace…1a6c
0x34b655…2a6f
6 touches
3 conflicts
0x20317244…edb4
0x34b655…2a6f
4 touches
1 conflict
0x253bf197…1e1a
0x34b655…2a6f
4 touches
1 conflict
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x8047e9b2…9bb8
0x34b655…2a6f
4 touches
1 conflict
0x881fc98e…23d2
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity