← previous blocknext block →recent activity
Analyzing
Block #106,951,695
51 transactions · 45 stateful · 2026-09-22 05:27:56 UTC
Parallelism
63/100
Blocked
78%
Avg conflicts / tx
2.9
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #106,951,695 · 51 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w29w313w114w215w326w427w528w629w730w834w935w136w237w438w539w642w1043w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0x125f12…a50b
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x65903ef9…2567
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x94dabb65…43a3
0x34b655…2a6f
10 touches
10 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity