← previous blocknext block →recent activity
Analyzing
Block #106,789,955
22 transactions · 16 stateful · 2026-09-21 15:53:49 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,789,955 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w010w111w012w114w115w217w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7e16629…11b7
0x34b655…2a6f
8 touches
6 conflicts
0x6aa06870…2fdd
0x34b655…2a6f
8 touches
6 conflicts
0xaa243ded…c0d0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe606c549…edc7
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xc7e166290c…5411b7
Audit this contract →
← previous block·next block →recent activity