← previous blocknext block →recent activity
Analyzing
Block #103,213,718
17 transactions · 17 stateful · 2026-09-09 03:07:13 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,213,718 · 17 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
1w02w04w07w110w111w212w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bea7638…9624
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x6d8ad688…4bf5
0xa6afd3…d132
4 touches
1 conflict
0x0505bae8…b4fb
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
6 conflicts on slot 0x6bea7638ac…ec9624
Audit this contract →
← previous block·next block →recent activity