← previous blocknext block →recent activity

Analyzing

Block #106,189,987

20 transactions · 18 stateful · 2026-09-19 13:33:11 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,189,987  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x67a56c8b…f955

0x34b655…2a6f

6 touches
3 conflicts

0xb935707a…140f

0x34b655…2a6f

6 touches
3 conflicts

0xf90c6521…d8f0

0x34b655…2a6f

4 touches
1 conflict

0x2cd2af6f…b80f

0x34b655…2a6f

4 touches
1 conflict

0x4073f47e…39e6

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x9167c873…748f

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 0x67a56c8b2e…d7f955

← previous block·next block →recent activity