← previous blocknext block →recent activity
Analyzing
Block #106,185,950
33 transactions · 32 stateful · 2026-09-19 13:12:52 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
2.7
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,185,950 · 33 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w28w212w313w216w419w522w623w724w825w926w1027w1028w1129w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2631b5d1…886b
0x34b655…2a6f
18 touches
36 conflicts
0xfa66bdd0…45f5
0x34b655…2a6f
16 touches
28 conflicts
0xd597209e…9800
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xb654bd89…a83b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0x2631b5d114…a7886b
Audit this contract →
← previous block·next block →recent activity