← previous blocknext block →recent activity

Analyzing

Block #108,344,233

16 transactions · 16 stateful · 2026-09-27 02:19:18 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,344,233  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1679b727…0208

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x152f8e3d…3da0

0x34b655…2a6f

6 touches
3 conflicts

0xd4230a60…bd13

0x34b655…2a6f

6 touches
3 conflicts

0xf5dc501b…831c

0x34b655…2a6f

6 touches
3 conflicts

0x3da6ec2b…b836

0x34b655…2a6f

6 touches
3 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

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 0x1679b7275f…f90208

← previous block·next block →recent activity