← previous blocknext block →recent activity
Analyzing
Block #106,931,195
30 transactions · 28 stateful · 2026-09-22 03:44:45 UTC
Parallelism
57/100
Blocked
68%
Avg conflicts / tx
2.6
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,931,195 · 30 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w411w512w614w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
18 touches
36 conflicts
0x810a3aa2…0227
0x34b655…2a6f
18 touches
36 conflicts
0xb6a59002…65eb
0x34b655…2a6f
16 touches
28 conflicts
0x3780a34a…b50a
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0xfac61869…a560
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity