← previous blocknext block →recent activity
Analyzing
Block #87,920,686
31 transactions · 23 stateful · 2026-07-15 13:05:27 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,920,686 · 31 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
2w03w14w213w014w117w018w119w220w321w324w425w428w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
10 touches
10 conflicts
0x731f2745…9370
0xa6afd3…d132
8 touches
6 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x7561f24a…4522
0x34b655…2a6f
6 touches
3 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity