← previous blocknext block →recent activity

Analyzing

Block #106,931,575

24 transactions · 24 stateful · 2026-09-22 03:46:40 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.92

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,931,575  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x469dac8d…3411

0x34b655…2a6f

10 touches
10 conflicts

0x155e52ca…fac7

0x34b655…2a6f

10 touches
10 conflicts

0x3740f434…cccb

0x34b655…2a6f

8 touches
6 conflicts

0x66511956…e9dc

0x34b655…2a6f

8 touches
6 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

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 0x469dac8dcd…223411

← previous block·next block →recent activity