← previous blocknext block →recent activity
Analyzing
Block #86,634,275
28 transactions · 20 stateful · 2026-07-09 13:42:43 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,634,275 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w113w214w018w024w125w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda46a376…f6a6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x31eb8b3e…c801
0x34b655…2a6f
4 touches
1 conflict
0x404260ba…42c5
0x34b655…2a6f
4 touches
1 conflict
0x42767e6e…020d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x87ee379a…cd9e
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
3 conflicts on slot 0xda46a376d7…59f6a6
Audit this contract →
← previous block·next block →recent activity