← previous blocknext block →recent activity
Analyzing
Block #93,339,524
20 transactions · 18 stateful · 2026-08-05 11:50:47 UTC
Parallelism
60/100
Blocked
39%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,339,524 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w110w211w313w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3e4969…39e9
0x34b655…2a6f
12 touches
15 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
10 touches
10 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0x216ffe66…1f94
0x34b655…2a6f
6 touches
3 conflicts
0x2385516f…eca5
0x34b655…2a6f
6 touches
3 conflicts
0x69473e5b…cb2a
0x34b655…2a6f
6 touches
3 conflicts
0x94de4d05…ad01
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
15 conflicts on slot 0xac3e4969cf…1739e9
Audit this contract →
← previous block·next block →recent activity