← previous blocknext block →recent activity

Analyzing

Block #106,950,885

22 transactions · 20 stateful · 2026-09-22 05:23:51 UTC

Parallelism

82/100

Blocked

30%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,950,885  ·  22 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

0xd844fa50…f124

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x1d81790c…b9f7

0x34b655…2a6f

4 touches
1 conflict

0x1f396cee…862f

0x34b655…2a6f

4 touches
1 conflict

0x23769ebc…c8ed

0x34b655…2a6f

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

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

1 conflict on slot 0xd844fa5048…32f124

← previous block·next block →recent activity