← previous blocknext block →recent activity

Analyzing

Block #106,540,224

23 transactions · 22 stateful · 2026-09-20 18:55:57 UTC

Parallelism

57/100

Blocked

45%

Avg conflicts / tx

1.7

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,540,224  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xcc973852…d99a

0x34b655…2a6f

16 touches
28 conflicts

0x2a2896a0…2a0a

0x34b655…2a6f

12 touches
15 conflicts

0xecd87a39…d9c5

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4bfdcd51…9b58

0x34b655…2a6f

6 touches
3 conflicts

0x9dd0a735…4d04

0x34b655…2a6f

6 touches
3 conflicts

0xc9a8c9ab…cd37

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

28 conflicts on slot 0xcc973852c0…82d99a

← previous block·next block →recent activity