← previous blocknext block →recent activity
Analyzing
Block #86,502,571
17 transactions · 13 stateful · 2026-07-08 23:00:55 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,502,571 · 17 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
5w06w17w28w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59a54ff4…d21b
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x4797cebc…5c38
0x34b655…2a6f
6 touches
3 conflicts
0xb6aedce9…a483
0x34b655…2a6f
6 touches
3 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
6 touches
3 conflicts
0x3674075e…02b7
0x34b655…2a6f
6 touches
3 conflicts
0x8631c06c…1922
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
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 0x59a54ff481…17d21b
Audit this contract →
← previous block·next block →recent activity