← previous blocknext block →recent activity
Analyzing
Block #86,904,932
13 transactions · 12 stateful · 2026-07-10 19:52:23 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,904,932 · 13 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
3w05w16w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3be33cca…0fff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x11359bd0…444a
0x34b655…2a6f
4 touches
1 conflict
0x1a0d7ec9…d134
0x34b655…2a6f
4 touches
1 conflict
0x1b89bfcf…8505
0x34b655…2a6f
4 touches
1 conflict
0x1b89bfcf…8506
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…1000
0x34b655…2a6f
4 touches
1 conflict
0x5ed58b36…c5e5
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 0x3be33cca63…660fff
Audit this contract →
← previous block·next block →recent activity