← previous blocknext block →recent activity

Analyzing

Block #106,191,790

18 transactions · 17 stateful · 2026-09-19 13:42:16 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,191,790  ·  18 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

0x74c5eacc…8c94

0x34b655…2a6f

8 touches
6 conflicts

0xf79df061…e005

0xe52b14…7230

6 touches
3 conflicts

0x8ffa3328…ce11

0xe52b14…7230

6 touches
3 conflicts

0x315e07b8…9823

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

0x34b655…2a6f

4 touches
1 conflict

0x4abfb389…18f4

0x34b655…2a6f

4 touches
1 conflict

0x6368f6c9…1c74

0x34b655…2a6f

4 touches
1 conflict

0x6dfcc76a…0759

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 0x74c5eaccd3…b48c94

← previous block·next block →recent activity