← previous blocknext block →recent activity
Analyzing
Block #107,841,344
75 transactions · 65 stateful · 2026-09-25 08:08:18 UTC
Parallelism
76/100
Blocked
78%
Avg conflicts / tx
3.28
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #107,841,344 · 75 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
1w02w13w17w08w19w210w312w415w016w118w220w221w338w239w540w150w351w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x3aecae9d…98ee
0xd32edf…ff58
19 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x422d5490…52d9
0x34b655…2a6f
14 touches
21 conflicts
0xa0a8c7a5…3422
0x34b655…2a6f
12 touches
15 conflicts
0x3ff9db2e…22f6
0x34b655…2a6f
12 touches
15 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
10 touches
10 conflicts
0x545e527e…0eb0
0x34b655…2a6f
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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity