← previous blocknext block →recent activity

Analyzing

Block #109,004,063

29 transactions · 22 stateful · 2026-09-29 09:45:57 UTC

Parallelism

90/100

Blocked

32%

Avg conflicts / tx

0.34

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #109,004,063  ·  29 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x52c17a…f6f4

4 touches
1 conflict

0x19ad3f01…022a

0x52c17a…f6f4

4 touches
1 conflict

0x6955017e…6fe7

0x52c17a…f6f4

4 touches
1 conflict

0xaea3a21e…c680

0x52c17a…f6f4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity