← previous blocknext block →recent activity

Analyzing

Block #106,931,917

21 transactions · 20 stateful · 2026-09-22 03:48:23 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,931,917  ·  21 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

0x23769ebc…c8ed

0x34b655…2a6f

10 touches
10 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

8 touches
6 conflicts

0xba1edffb…323e

0x34b655…2a6f

6 touches
3 conflicts

0xf1ad394c…ae23

0x34b655…2a6f

6 touches
3 conflicts

0x96784e2c…cb41

0x34b655…2a6f

6 touches
3 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x00216970…a965

0x34b655…2a6f

6 touches
3 conflicts

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 0x23769ebc9a…0ec8ed

← previous block·next block →recent activity