← previous blocknext block →recent activity
Analyzing
Block #87,288,068
12 transactions · 9 stateful · 2026-07-12 14:33:38 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,288,068 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0x70d66bd9…0ffa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x13661605…ecbd
0x34b655…2a6f
4 touches
1 conflict
0x22af2e4e…609c
0x34b655…2a6f
4 touches
1 conflict
0x34cbc614…e779
0x34b655…2a6f
4 touches
1 conflict
0x60c4435a…22ca
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity