← previous blocknext block →recent activity
Analyzing
Block #106,916,661
54 transactions · 45 stateful · 2026-09-22 02:31:36 UTC
Parallelism
72/100
Blocked
76%
Avg conflicts / tx
2.24
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,916,661 · 54 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w07w19w112w213w314w415w516w617w723w124w231w542w1046w549w752w1353w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x593f95a5…b6e0
0x34b655…2a6f
10 touches
10 conflicts
0x5c2df7aa…8f80
0x34b655…2a6f
10 touches
10 conflicts
0xc36633d8…eee7
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity