← previous blocknext block →recent activity

Analyzing

Block #107,440,698

21 transactions · 21 stateful · 2026-09-23 22:29:42 UTC

Parallelism

62/100

Blocked

38%

Avg conflicts / tx

1.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,440,698  ·  21 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

0xf5dc501b…831c

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

10 touches
10 conflicts

0xb066c72c…87d2

0x34b655…2a6f

6 touches
3 conflicts

0xa69bb4e1…f2bb

0x34b655…2a6f

6 touches
3 conflicts

0xe5797227…88f7

0x34b655…2a6f

5 touches
3 conflicts

0xd739490d…821e

0x34b655…2a6f

5 touches
3 conflicts

0xaf7f13f9…a2c9

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 0xf5dc501bf7…74831c

← previous block·next block →recent activity