← previous blocknext block →recent activity
Analyzing
Block #86,846,964
13 transactions · 9 stateful · 2026-07-10 13:24:43 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,846,964 · 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
1w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x6f42e42b…5717
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5397b810…e7e4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac28ff95…4764
0x34b655…2a6f
4 touches
1 conflict
0xdf06241e…adf9
0x34b655…2a6f
4 touches
1 conflict
0xe88872e2…9975
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
1 conflict on slot 0x2bfb71b55d…123a05
Audit this contract →
← previous block·next block →recent activity