← previous blocknext block →recent activity
Analyzing
Block #106,945,077
43 transactions · 36 stateful · 2026-09-22 04:54:37 UTC
Parallelism
72/100
Blocked
64%
Avg conflicts / tx
2.07
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,945,077 · 43 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w28w09w110w212w013w114w218w019w120w121w222w323w426w427w528w629w530w731w832w933w1037w340w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a286811…499f
0x34b655…2a6f
20 touches
45 conflicts
0x858e40c0…7e30
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xcb21158b…f18d
0x34b655…2a6f
12 touches
15 conflicts
0xdb4c0eb3…f7b9
0x34b655…2a6f
10 touches
10 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0bfb99f2…9779
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
45 conflicts on slot 0x2a28681175…0a499f
Audit this contract →
← previous block·next block →recent activity