← previous blocknext block →recent activity
Analyzing
Block #87,285,038
10 transactions · 8 stateful · 2026-07-12 14:13:22 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,285,038 · 10 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
3w04w15w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x333c820d…10c1
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdf06241e…adf9
0x34b655…2a6f
4 touches
1 conflict
0x0a6a5b44…d0e5
0x34b655…2a6f
4 touches
1 conflict
0x0c4777a2…2176
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
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
3 conflicts on slot 0x333c820d6f…7d10c1
Audit this contract →
← previous block·next block →recent activity