← previous blocknext block →recent activity
Analyzing
Block #106,922,206
32 transactions · 30 stateful · 2026-09-22 02:59:30 UTC
Parallelism
53/100
Blocked
67%
Avg conflicts / tx
2.59
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,922,206 · 32 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
1w03w04w15w06w18w09w110w211w312w413w514w615w716w817w918w1019w1120w1222w223w327w1328w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7462b8f2…6312
0x34b655…2a6f
18 touches
36 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0x9eef1610…1564
0x34b655…2a6f
14 touches
21 conflicts
0x1f99a64d…d760
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0x050d7a8a…67d0
0x34b655…2a6f
8 touches
6 conflicts
0xe07f244e…cdf2
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
36 conflicts on slot 0x7462b8f2c2…8d6312
Audit this contract →
← previous block·next block →recent activity