← previous blocknext block →recent activity
Analyzing
Block #106,953,512
43 transactions · 38 stateful · 2026-09-22 05:37:05 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.7
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,953,512 · 43 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w28w010w011w116w217w318w419w525w126w128w629w730w832w1036w137w1138w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x051d02f4…5aa2
0x34b655…2a6f
18 touches
36 conflicts
0x51087f5a…61f7
0x34b655…2a6f
14 touches
21 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3eb48ea2…eef2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x5ce28434…11ee
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 0x051d02f481…0d5aa2
Audit this contract →
← previous block·next block →recent activity