← previous blocknext block →recent activity

Analyzing

Block #105,844,001

18 transactions · 18 stateful · 2026-09-18 08:30:51 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,844,001  ·  18 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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x5a548af5…0eb0

0x34b655…2a6f

6 touches
3 conflicts

0x27e92642…b1c1

0x34b655…2a6f

6 touches
3 conflicts

0x3aed8a17…20f9

0x34b655…2a6f

4 touches
1 conflict

0x6c7c1a4b…5751

0x34b655…2a6f

4 touches
1 conflict

0x735bcbf6…13e5

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x7c216fca…20cb

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

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity