← previous blocknext block →recent activity

Analyzing

Block #108,658,222

20 transactions · 18 stateful · 2026-09-28 04:40:05 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,658,222  ·  20 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

8 touches
6 conflicts

0xc2fe6ed6…f8be

0x34b655…2a6f

6 touches
3 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

6 touches
3 conflicts

0xf5dc501b…831c

0x34b655…2a6f

6 touches
3 conflicts

0x30421e78…84f9

0x34b655…2a6f

4 touches
1 conflict

0x377d8db7…c362

0x34b655…2a6f

4 touches
1 conflict

0x3b8da5cc…e045

0x34b655…2a6f

4 touches
1 conflict

0x3d13406e…eff1

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

← previous block·next block →recent activity