← previous blocknext block →recent activity
Analyzing
Block #107,651,419
108 transactions · 104 stateful · 2026-09-24 16:11:02 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
1.46
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #107,651,419 · 108 txs across 20 waves · depth 20
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
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w310w112w213w414w515w616w719w820w986w487w5101w16104w19105w10106w11107w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0xea9a3529…ef85
0xd32edf…ff58
11 touches
15 conflicts
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0xc3483764…f299
0x1b6862…e19c
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity