← previous blocknext block →recent activity

Analyzing

Block #108,503,877

24 transactions · 22 stateful · 2026-09-27 15:42:49 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,503,877  ·  24 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

0xf5dc501b…831c

0x34b655…2a6f

8 touches
6 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

8 touches
6 conflicts

0x2bfa532a…1d25

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x5e882511…59d1

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x190b178a…c154

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 0xf5dc501bf7…74831c

← previous block·next block →recent activity