← previous blocknext block →recent activity
Analyzing
Block #87,616,507
22 transactions · 21 stateful · 2026-07-14 03:10:53 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,616,507 · 22 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
6w07w08w19w210w311w415w116w217w118w319w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x4e970d38…d1c4
0x34b655…2a6f
10 touches
10 conflicts
0x68b75835…d6f3
0x34b655…2a6f
8 touches
6 conflicts
0xa740c36a…99d3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe6fd65c0…3a8a
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x25329a48…4e00
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity