← previous blocknext block →recent activity

Analyzing

Block #106,917,879

18 transactions · 17 stateful · 2026-09-22 02:37:43 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,917,879  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x49acf7ff…912d

0x34b655…2a6f

12 touches
15 conflicts

0x4786839b…c29a

0x34b655…2a6f

10 touches
10 conflicts

0xf2ed177c…74be

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x518221db…65f7

0x34b655…2a6f

6 touches
3 conflicts

0xdb98ecdf…61bd

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

15 conflicts on slot 0x49acf7ffd5…4b912d

← previous block·next block →recent activity