← previous blocknext block →recent activity

Analyzing

Block #106,933,931

19 transactions · 17 stateful · 2026-09-22 03:58:31 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,933,931  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x388ab72e…e6e6

0x34b655…2a6f

10 touches
10 conflicts

0x7462b8f2…6312

0x34b655…2a6f

10 touches
10 conflicts

0xccebf5c5…8758

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd7e30f48…ec17

0xa6afd3…d132

6 touches
3 conflicts

0x4dc884eb…e337

0xa6afd3…d132

4 touches
1 conflict

0x51cd9c49…ad66

0xa6afd3…d132

4 touches
1 conflict

0xee1e9794…c93f

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

10 conflicts on slot 0x388ab72e91…70e6e6

← previous block·next block →recent activity