← previous blocknext block →recent activity
Analyzing
Block #106,922,050
31 transactions · 31 stateful · 2026-09-22 02:58:43 UTC
Parallelism
48/100
Blocked
61%
Avg conflicts / tx
2.48
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,922,050 · 31 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
1w03w04w15w26w37w48w59w610w711w112w813w914w1015w1116w1217w1318w1419w1520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf64e5e6…75e8
0x34b655…2a6f
18 touches
36 conflicts
0x7462b8f2…6312
0x34b655…2a6f
18 touches
36 conflicts
0x085d5985…c9cd
0x34b655…2a6f
16 touches
28 conflicts
0x1f99a64d…d760
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
16 touches
28 conflicts
0x589aa18a…4146
0x34b655…2a6f
6 touches
3 conflicts
0x469dac8d…3411
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 0xdf64e5e6b0…c975e8
Audit this contract →
← previous block·next block →recent activity