← previous blocknext block →recent activity
Analyzing
Block #87,664,312
14 transactions · 8 stateful · 2026-07-14 08:30:22 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,664,312 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0x0cc02c…75b2
2 touches
0 conflicts
0x00000000…0006
0x0cc02c…75b2
2 touches
0 conflicts
0x4e954e76…0358
0x0cc02c…75b2
2 touches
0 conflicts
0xbb304993…057a
0x0cc02c…75b2
2 touches
0 conflicts
0x08330b36…ae29
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity