← previous blocknext block →recent activity

Analyzing

Block #108,482,445

20 transactions · 19 stateful · 2026-09-27 13:54:54 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,482,445  ·  20 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

0x5cb2ad15…0483

0x34b655…2a6f

6 touches
3 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xe513dcb3…ffbd

0xd32edf…ff58

5 touches
3 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x5969523e…5191

0x34b655…2a6f

4 touches
1 conflict

0x659933ab…e189

0x34b655…2a6f

4 touches
1 conflict

0x6d5d1fb5…86a7

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

3 conflicts on slot 0x5cb2ad1503…770483

← previous block·next block →recent activity