← previous blocknext block →recent activity
Analyzing
Block #106,235,242
39 transactions · 37 stateful · 2026-09-19 17:21:03 UTC
Parallelism
80/100
Blocked
68%
Avg conflicts / tx
1.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,235,242 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w28w211w212w318w419w320w421w522w526w635w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x996984e1…123d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be16
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x05e1eba1…6491
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
15 conflicts on slot 0x996984e1d8…77123d
Audit this contract →
← previous block·next block →recent activity