← previous blocknext block →recent activity
Analyzing
Block #86,805,831
18 transactions · 14 stateful · 2026-07-10 08:49:39 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,805,831 · 18 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
1w02w13w04w15w26w09w310w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x3bca5b95…9ee9
0x34b655…2a6f
6 touches
3 conflicts
0x48260180…a411
0x34b655…2a6f
6 touches
3 conflicts
0x48260180…a412
0x34b655…2a6f
6 touches
3 conflicts
0x39cc2185…caca
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…cacb
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity