← previous blocknext block →recent activity
Analyzing
Block #86,833,711
30 transactions · 14 stateful · 2026-07-10 11:56:12 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,833,711 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
17w020w121w024w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17fbe072…2ea6
0x34b655…2a6f
6 touches
3 conflicts
0x7ae195ed…3632
0x34b655…2a6f
6 touches
3 conflicts
0xf7ab945c…597e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe2264392…d5f4
0x34b655…2a6f
4 touches
1 conflict
0xe2307994…acad
0x34b655…2a6f
4 touches
1 conflict
0x21a3ddc9…fe40
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 0x17fbe07235…a42ea6
Audit this contract →
← previous block·next block →recent activity