← previous blocknext block →recent activity
Analyzing
Block #107,823,565
53 transactions · 47 stateful · 2026-09-25 06:38:50 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
1.75
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #107,823,565 · 53 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w010w112w214w115w318w019w120w221w323w324w428w429w530w635w338w448w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x839c0c71…bada
0x34b655…2a6f
14 touches
21 conflicts
0xa2c4d203…05b6
0x34b655…2a6f
12 touches
15 conflicts
0x5f251b96…6054
0x34b655…2a6f
10 touches
10 conflicts
0x6a9e408e…3721
0x34b655…2a6f
10 touches
10 conflicts
0xae65f1ba…2f37
0x34b655…2a6f
10 touches
10 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
10 touches
10 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
28 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity