← previous blocknext block →recent activity

Analyzing

Block #106,932,879

19 transactions · 19 stateful · 2026-09-22 03:53:13 UTC

Parallelism

47/100

Blocked

58%

Avg conflicts / tx

1.68

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,932,879  ·  19 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

0x6c26d635…1bbf

0x34b655…2a6f

14 touches
21 conflicts

0x643113d0…43d7

0x34b655…2a6f

10 touches
10 conflicts

0x4786839b…c29a

0x34b655…2a6f

10 touches
10 conflicts

0xccebf5c5…8758

0x34b655…2a6f

10 touches
10 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x79dcc7d9…caaa

0x34b655…2a6f

8 touches
6 conflicts

0xf75d2778…4de5

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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

21 conflicts on slot 0x6c26d63540…461bbf

← previous block·next block →recent activity