← previous blocknext block →recent activity

Analyzing

Block #109,142,748

22 transactions · 19 stateful · 2026-09-29 21:25:28 UTC

Parallelism

82/100

Blocked

32%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #109,142,748  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa8370149…b7e7

0x34b655…2a6f

8 touches
6 conflicts

0x3d93ad2c…e747

0x34b655…2a6f

8 touches
6 conflicts

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0x3fa1fac4…826c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x3a3a32d7…b5e3

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

6 conflicts on slot 0xa837014982…8cb7e7

← previous block·next block →recent activity