← previous blocknext block →recent activity
Analyzing
Block #86,816,369
21 transactions · 18 stateful · 2026-07-10 10:00:04 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,816,369 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w311w012w114w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x9f46101d…b728
0x065c9d…c394
4 touches
1 conflict
0x00873542…6db6
0x34b655…2a6f
4 touches
1 conflict
0x55642f63…03d6
0x34b655…2a6f
4 touches
1 conflict
0x806b072c…4e98
0x34b655…2a6f
4 touches
1 conflict
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity