← previous blocknext block →recent activity
Analyzing
Block #103,993,880
22 transactions · 21 stateful · 2026-09-11 20:43:17 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,993,880 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w07w18w212w313w415w516w617w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda69449…1d3b
0x34b655…2a6f
12 touches
15 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
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 0xfda694493e…261d3b
Audit this contract →
← previous block·next block →recent activity