← previous blocknext block →recent activity
Analyzing
Block #87,420,821
22 transactions · 16 stateful · 2026-07-13 05:21:26 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,420,821 · 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
2w08w19w210w314w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b7559b6…6072
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
6 touches
3 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
6 touches
3 conflicts
0xda46a376…f6a6
0x34b655…2a6f
4 touches
1 conflict
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x0866e398…2184
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
6 conflicts on slot 0x5b7559b642…706072
Audit this contract →
← previous block·next block →recent activity