← previous blocknext block →recent activity
Analyzing
Block #86,833,845
12 transactions · 7 stateful · 2026-07-10 11:57:05 UTC
Parallelism
83/100
Blocked
14%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,833,845 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b6b57d4…7587
0x34b655…2a6f
4 touches
1 conflict
0x2ddad553…f810
0x34b655…2a6f
4 touches
1 conflict
0x2ddad553…f811
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xdf7963b5…5eef
0x34b655…2a6f
4 touches
1 conflict
0xe15bff66…24a9
0x34b655…2a6f
4 touches
1 conflict
0x912fb14a…f568
0x34b655…2a6f
3 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 0x2b6b57d40d…357587
Audit this contract →
← previous block·next block →recent activity