← previous blocknext block →recent activity

Analyzing

Block #108,568,132

20 transactions · 19 stateful · 2026-09-27 21:06:28 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,568,132  ·  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

0xaf4b5f6f…49cc

0x34b655…2a6f

6 touches
3 conflicts

0x66027c66…f69c

0x065c9d…c394

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb86

0x1b6862…e19c

4 touches
1 conflict

0x00fdfea4…a423

0x34b655…2a6f

4 touches
1 conflict

0x127388ce…0354

0x34b655…2a6f

4 touches
1 conflict

0x1abfd3ae…2999

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 0xaf4b5f6fbd…2c49cc

← previous block·next block →recent activity