← previous blocknext block →recent activity
Analyzing
Block #86,341,768
16 transactions · 15 stateful · 2026-07-08 05:06:23 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,341,768 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w212w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x830b63a6…8105
0x34b655…2a6f
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0x8afb84ca…2662
0xa6afd3…d132
3 touches
1 conflict
0x08b8e539…b9f9
0x754704…b603
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0x2b9c6652…d14e
0x754704…b603
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 0x830b63a692…148105
Audit this contract →
← previous block·next block →recent activity