← previous blocknext block →recent activity
Analyzing
Block #103,221,804
21 transactions · 21 stateful · 2026-09-09 03:47:58 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #103,221,804 · 21 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
1w06w17w212w314w417w018w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf21aeb71…92a2
0x34b655…2a6f
10 touches
10 conflicts
0xd9722304…6ed0
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x46c14e01…ff09
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
10 conflicts on slot 0xf21aeb71b5…8b92a2
Audit this contract →
← previous block·next block →recent activity