← previous blocknext block →recent activity
Analyzing
Block #87,418,197
14 transactions · 13 stateful · 2026-07-13 05:03:55 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,418,197 · 14 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
1w02w14w25w37w39w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4b86ec…900f
0x34b655…2a6f
8 touches
6 conflicts
0x366f651e…6100
0x34b655…2a6f
8 touches
6 conflicts
0x79bdf655…91f2
0x34b655…2a6f
6 touches
3 conflicts
0x8866dae4…ac60
0x34b655…2a6f
6 touches
3 conflicts
0x4c214bb3…c5d3
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
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 0xea4b86ec74…1a900f
Audit this contract →
← previous block·next block →recent activity