← previous blocknext block →recent activity

Analyzing

Block #108,684,614

23 transactions · 21 stateful · 2026-09-28 06:53:02 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #108,684,614  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x0cf0cbef…f0dc

0x34b655…2a6f

10 touches
10 conflicts

0x7f8e3158…9dfd

0x34b655…2a6f

10 touches
10 conflicts

0x8b780b26…f5ff

0x34b655…2a6f

10 touches
10 conflicts

0xada087b9…4aca

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x4c572488…35d9

0x34b655…2a6f

8 touches
6 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

8 touches
6 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0x0cf0cbeffd…75f0dc

← previous block·next block →recent activity