← previous blocknext block →recent activity

Analyzing

Block #108,713,221

24 transactions · 22 stateful · 2026-09-28 09:17:15 UTC

Parallelism

71/100

Blocked

32%

Avg conflicts / tx

0.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,713,221  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8b780b26…f5ff

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x4c572488…35d9

0x34b655…2a6f

6 touches
3 conflicts

0x4cff6b80…47a8

0x34b655…2a6f

6 touches
3 conflicts

0x88fc2a68…3918

0x34b655…2a6f

6 touches
3 conflicts

0xada087b9…4aca

0x34b655…2a6f

6 touches
3 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

6 touches
3 conflicts

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 0x8b780b2668…85f5ff

← previous block·next block →recent activity