← previous blocknext block →recent activity

Analyzing

Block #106,949,327

20 transactions · 20 stateful · 2026-09-22 05:16:01 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,949,327  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd9a9c481…8916

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xe22ab637…7a8e

0x34b655…2a6f

4 touches
1 conflict

0x1d81790c…b9f7

0x34b655…2a6f

4 touches
1 conflict

0x29ece348…5373

0x34b655…2a6f

4 touches
1 conflict

0x300ff960…d3cd

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 0x8590b69238…6ab267

← previous block·next block →recent activity