← previous blocknext block →recent activity
Analyzing
Block #106,916,416
34 transactions · 32 stateful · 2026-09-22 02:30:22 UTC
Parallelism
62/100
Blocked
56%
Avg conflicts / tx
1.82
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,916,416 · 34 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
3w04w16w010w011w112w213w314w416w517w618w719w820w921w1022w1123w1229w130w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5eb3c33…0e3a
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x8469771e…1c75
0x34b655…2a6f
16 touches
28 conflicts
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x803d32b5…8094
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
36 conflicts on slot 0xe5eb3c3335…0c0e3a
Audit this contract →
← previous block·next block →recent activity