← previous blocknext block →recent activity
Analyzing
Block #86,830,599
18 transactions · 14 stateful · 2026-07-10 11:35:22 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,830,599 · 18 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
1w04w15w26w310w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0xe3e5befe…fcda
0x34b655…2a6f
4 touches
1 conflict
0xe3e5befe…fcdb
0x34b655…2a6f
4 touches
1 conflict
0x25e0daa5…d833
0x34b655…2a6f
4 touches
1 conflict
0x42d8b371…bb43
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xf51ec09cc1…a1b4a9
Audit this contract →
← previous block·next block →recent activity