← previous blocknext block →recent activity
Analyzing
Block #106,954,222
39 transactions · 34 stateful · 2026-09-22 05:40:40 UTC
Parallelism
59/100
Blocked
68%
Avg conflicts / tx
3.03
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,954,222 · 39 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w18w09w110w211w314w415w516w617w718w819w920w1021w1123w1224w1325w1433w135w136w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0x56755b2b…8d44
0x34b655…2a6f
16 touches
28 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
16 touches
28 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
16 touches
28 conflicts
0xf99548c6…30b3
0x37db7f…ec7b
16 touches
28 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
16 touches
28 conflicts
0x5f72d58f…c445
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity