← previous blocknext block →recent activity

Analyzing

Block #108,684,768

27 transactions · 20 stateful · 2026-09-28 06:53:49 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,684,768  ·  27 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa03c2a35…52e6

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x23769ebc…c8ed

0x34b655…2a6f

6 touches
3 conflicts

0x6bcce472…9579

0x34b655…2a6f

6 touches
3 conflicts

0xddf10453…d774

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0xa53939ed…26f5

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

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

3 conflicts on slot 0xa03c2a355d…ca52e6

← previous block·next block →recent activity