← previous blocknext block →recent activity
Analyzing
Block #107,278,009
36 transactions · 32 stateful · 2026-09-23 08:50:48 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.78
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,278,009 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w08w19w215w321w424w125w526w128w529w630w731w832w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518221db…65f7
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6bd4088b…62b9
0x34b655…2a6f
12 touches
15 conflicts
0x49acf7ff…912d
0x34b655…2a6f
8 touches
6 conflicts
0x333bf9c2…0730
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x39bc76e0…ac05
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
36 conflicts on slot 0x518221db7f…5465f7
Audit this contract →
← previous block·next block →recent activity