← previous blocknext block →recent activity
Analyzing
Block #106,585,227
33 transactions · 30 stateful · 2026-09-20 22:42:26 UTC
Parallelism
48/100
Blocked
70%
Avg conflicts / tx
3.3
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,585,227 · 33 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w39w110w213w415w516w618w719w820w922w1123w1224w1326w1527w1630w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3b4402…74e6
0x34b655…2a6f
24 touches
66 conflicts
0xdc7321b7…5f0a
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xab41643c…f9bf
0x34b655…2a6f
8 touches
6 conflicts
0xff4fd690…957d
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x38c6ff01…689f
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
66 conflicts on slot 0xaa3b44023d…a974e6
Audit this contract →
← previous block·next block →recent activity