← previous blocknext block →recent activity
Analyzing
Block #87,331,287
20 transactions · 20 stateful · 2026-07-12 19:22:38 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,331,287 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w010w111w113w214w117w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b18ba0…f380
0x34b655…2a6f
8 touches
6 conflicts
0x03b16972…8f62
0x34b655…2a6f
6 touches
3 conflicts
0x71cbd5f6…e66e
0x34b655…2a6f
6 touches
3 conflicts
0x7b2a6010…6b9f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xadae3c90…7572
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
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
6 conflicts on slot 0xa8b18ba0f2…07f380
Audit this contract →
← previous block·next block →recent activity