← previous blocknext block →recent activity
Analyzing
Block #87,341,302
12 transactions · 11 stateful · 2026-07-12 20:29:36 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,341,302 · 12 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
5w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe85e763f…3b25
0x34b655…2a6f
6 touches
3 conflicts
0xfebaf6fc…61b5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8f6f7a3…f563
0x34b655…2a6f
4 touches
1 conflict
0xc8f6f7a3…f564
0x34b655…2a6f
4 touches
1 conflict
0xdad3be8c…a703
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 0xe85e763f0b…a63b25
Audit this contract →
← previous block·next block →recent activity