← previous blocknext block →recent activity

Analyzing

Block #107,813,580

23 transactions · 19 stateful · 2026-09-25 05:48:34 UTC

Parallelism

78/100

Blocked

42%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,813,580  ·  23 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

0x7c741add…25d6

0x34b655…2a6f

10 touches
10 conflicts

0xba522812…1f1f

0x34b655…2a6f

10 touches
10 conflicts

0x961c0cd9…0937

0x34b655…2a6f

8 touches
6 conflicts

0xe63c6702…03f3

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x6455c121…f808

0x34b655…2a6f

6 touches
3 conflicts

0x64aad777…d945

0x34b655…2a6f

6 touches
3 conflicts

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 0x7c741add3e…2b25d6

← previous block·next block →recent activity