← previous blocknext block →recent activity

Analyzing

Block #108,495,004

18 transactions · 18 stateful · 2026-09-27 14:58:08 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,495,004  ·  18 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x16d77246…bac5

0x34b655…2a6f

4 touches
1 conflict

0x280aaa58…1c52

0x34b655…2a6f

4 touches
1 conflict

0x3243e72f…1f6d

0x34b655…2a6f

4 touches
1 conflict

0x40d6d1e9…131e

0x34b655…2a6f

4 touches
1 conflict

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x5969523e…5191

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity