← previous blocknext block →recent activity

Analyzing

Block #107,823,770

16 transactions · 15 stateful · 2026-09-25 06:39:51 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.44

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #107,823,770  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xf5dc501b…831c

0x34b655…2a6f

12 touches
15 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

12 touches
15 conflicts

0xd739490d…821e

0x34b655…2a6f

10 touches
10 conflicts

0x3ba51d3a…7978

0x34b655…2a6f

8 touches
6 conflicts

0xa69bb4e1…f2bb

0x34b655…2a6f

8 touches
6 conflicts

0xd17684b1…a1d0

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity