← previous blocknext block →recent activity
Analyzing
Block #86,754,044
23 transactions · 19 stateful · 2026-07-10 03:03:53 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,754,044 · 23 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
1w04w07w08w09w111w113w214w315w420w021w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfeeef71e…8b3d
0x34b655…2a6f
8 touches
6 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
6 touches
3 conflicts
0x50e84e6c…287f
0x34b655…2a6f
4 touches
1 conflict
0x56f7a389…74fd
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity