← previous blocknext block →recent activity

Analyzing

Block #110,382,619

20 transactions · 18 stateful · 2026-10-04 05:26:38 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #110,382,619  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xdf64e5e6…75e8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x1d351a9b…f2dd

0x34b655…2a6f

4 touches
1 conflict

0x90a021f0…f922

0x34b655…2a6f

4 touches
1 conflict

0x9abad0e8…28a3

0x34b655…2a6f

4 touches
1 conflict

0xac95ccae…2678

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity