← previous blocknext block →recent activity
Analyzing
Block #86,712,812
12 transactions · 7 stateful · 2026-07-09 22:28:14 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,712,812 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64d353bf…54eb
0x34b655…2a6f
6 touches
3 conflicts
0x64d353bf…54ec
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x356f8a28…5791
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x50e84e6c…287f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x7fd4b0ef…1795
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 0x64d353bf38…8f54eb
Audit this contract →
← previous block·next block →recent activity