← previous blocknext block →recent activity
Analyzing
Block #86,293,503
26 transactions · 22 stateful · 2026-07-07 23:43:55 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,293,503 · 26 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
1w05w07w18w210w313w014w119w020w121w222w323w224w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x02598f88…e629
0xd32edf…ff58
7 touches
6 conflicts
0x11560115…bfc2
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x5138188e…796b
0x34b655…2a6f
6 touches
3 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0xd6aabe89…92f5
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity