← previous blocknext block →recent activity
Analyzing
Block #106,109,146
20 transactions · 18 stateful · 2026-09-19 06:46:20 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,109,146 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w210w211w212w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x961c0cd9…0937
0x34b655…2a6f
10 touches
10 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
8 touches
6 conflicts
0x543f4651…59d0
0x34b655…2a6f
8 touches
6 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
8 touches
6 conflicts
0x8b827935…5a44
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
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
10 conflicts on slot 0x961c0cd92c…d10937
Audit this contract →
← previous block·next block →recent activity