← previous blocknext block →recent activity
Analyzing
Block #106,923,333
23 transactions · 22 stateful · 2026-09-22 03:05:11 UTC
Parallelism
52/100
Blocked
55%
Avg conflicts / tx
1.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,923,333 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w711w812w913w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23769ebc…c8ed
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xab981df1…2941
0x34b655…2a6f
12 touches
15 conflicts
0x96784e2c…cb41
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xa66499c2…9f47
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x201b774d…c087
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
21 conflicts on slot 0x23769ebc9a…0ec8ed
Audit this contract →
← previous block·next block →recent activity