← previous blocknext block →recent activity
Analyzing
Block #86,809,996
14 transactions · 11 stateful · 2026-07-10 09:17:27 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,809,996 · 14 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bc5d643…38d8
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d9
0x34b655…2a6f
4 touches
1 conflict
0xc40c8e2b…b832
0x34b655…2a6f
4 touches
1 conflict
0x698e3c53…a4c4
0x34b655…2a6f
4 touches
1 conflict
0x1ffe7d94…61ea
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
2 touches
0 conflicts
0x7f8dee28…fb02
0x34b655…2a6f
2 touches
0 conflicts
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 0x0bc5d6431e…ab38d8
Audit this contract →
← previous block·next block →recent activity