← previous blocknext block →recent activity
Analyzing
Block #86,977,952
15 transactions · 13 stateful · 2026-07-11 04:00:15 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,977,952 · 15 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
1w04w05w16w18w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b95e778…d7d0
0x34b655…2a6f
6 touches
3 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x4da2c807…8775
0x34b655…2a6f
4 touches
1 conflict
0xf58b2d27…e4eb
0x34b655…2a6f
4 touches
1 conflict
0x59f58019…2973
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 0x2b95e778b5…e2d7d0
Audit this contract →
← previous block·next block →recent activity