← previous blocknext block →recent activity
Analyzing
Block #87,579,713
12 transactions · 10 stateful · 2026-07-13 23:04:48 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,579,713 · 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
3w04w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa5420e1f…3788
0x34b655…2a6f
6 touches
3 conflicts
0xc953cb03…3362
0x34b655…2a6f
4 touches
1 conflict
0x1d6ccfe1…0610
0x34b655…2a6f
4 touches
1 conflict
0x1d6ccfe1…0611
0x34b655…2a6f
4 touches
1 conflict
0x22b2393b…7c4d
0x34b655…2a6f
4 touches
1 conflict
0x43cea534…ddce
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity