← previous blocknext block →recent activity

Analyzing

Block #108,787,510

25 transactions · 20 stateful · 2026-09-28 15:31:22 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.08

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #108,787,510  ·  25 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8b780b26…f5ff

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x739123da…57f3

0x34b655…2a6f

4 touches
1 conflict

0x7bd229ad…63b2

0x34b655…2a6f

4 touches
1 conflict

0x88fc2a68…3918

0x34b655…2a6f

4 touches
1 conflict

0x9d394e92…9d5c

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity