← previous blocknext block →recent activity

Analyzing

Block #106,946,402

22 transactions · 21 stateful · 2026-09-22 05:01:18 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,946,402  ·  22 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

0xba1edffb…323e

0x34b655…2a6f

10 touches
10 conflicts

0xc8c615d4…5da3

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xa0998a89…1f5a

0x34b655…2a6f

6 touches
3 conflicts

0x72055767…d5a5

0x34b655…2a6f

4 touches
1 conflict

0x9375a764…dca1

0x34b655…2a6f

4 touches
1 conflict

0xa4a1ecf7…9e63

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

10 conflicts on slot 0xba1edffb42…64323e

← previous block·next block →recent activity