← previous blocknext block →recent activity
Analyzing
Block #103,211,210
12 transactions · 11 stateful · 2026-09-09 02:54:36 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,211,210 · 12 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
1w02w13w24w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc63169…68cc
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
6 touches
3 conflicts
0x1513b999…b52e
0x34b655…2a6f
6 touches
3 conflicts
0xf5d28bce…c32c
0x34b655…2a6f
6 touches
3 conflicts
0x0e216931…58c3
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0x5f40adf2…e754
0x34b655…2a6f
6 touches
3 conflicts
0x676707df…0e0a
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
3 conflicts on slot 0xffc631698e…cf68cc
Audit this contract →
← previous block·next block →recent activity