← previous blocknext block →recent activity
Analyzing
Block #93,484,718
20 transactions · 18 stateful · 2026-08-06 00:00:45 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,484,718 · 20 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
1w02w13w25w38w09w010w112w213w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7a12283f…b18a
0x2b46c0…1669
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
6 touches
3 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
6 touches
3 conflicts
0x1232aa2b…bc8a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity