← previous blocknext block →recent activity

Analyzing

Block #106,950,704

26 transactions · 21 stateful · 2026-09-22 05:22:57 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,950,704  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x4460fbdd…e9f6

0x34b655…2a6f

10 touches
10 conflicts

0x1c59817b…07e8

0x34b655…2a6f

8 touches
6 conflicts

0xfcc8f826…7c5f

0x34b655…2a6f

8 touches
6 conflicts

0xf67ba2c2…aa9c

0x34b655…2a6f

8 touches
6 conflicts

0xea79e6d3…68ad

0x34b655…2a6f

6 touches
3 conflicts

0xfaad154e…4d2f

0x34b655…2a6f

6 touches
3 conflicts

0x70986451…c6bd

0x34b655…2a6f

6 touches
3 conflicts

0xab981df1…2941

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 0x4460fbddff…b1e9f6

← previous block·next block →recent activity