← previous blocknext block →recent activity

Analyzing

Block #107,442,211

25 transactions · 24 stateful · 2026-09-23 22:37:19 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.36

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,442,211  ·  25 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

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x662d9b98…0f6b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x21214964…c0f8

0x34b655…2a6f

4 touches
1 conflict

0x4292a836…9ed5

0x34b655…2a6f

4 touches
1 conflict

0x4b41fd89…a810

0x34b655…2a6f

4 touches
1 conflict

0x5c1cc07a…b400

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

3 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity