← previous blocknext block →recent activity
Analyzing
Block #87,725,300
25 transactions · 20 stateful · 2026-07-14 15:18:31 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,725,300 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w310w411w512w617w218w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0x031b9f26…67e6
0x34b655…2a6f
10 touches
10 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
10 touches
10 conflicts
0xc2186704…5cc3
0x34b655…2a6f
10 touches
10 conflicts
0xd8b006b5…a95d
0x34b655…2a6f
10 touches
10 conflicts
0xeebaa043…0d3c
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity