← previous blocknext block →recent activity

Analyzing

Block #105,929,870

22 transactions · 20 stateful · 2026-09-18 15:43:56 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,929,870  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd6265424…0d3a

0x851145…3f07

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0x35c68080…aace

0x851145…3f07

6 touches
3 conflicts

0xf0a8a215…8f23

0x851145…3f07

6 touches
3 conflicts

0x915c095e…c1e5

0x34ae4d…3fc5

4 touches
1 conflict

0xcfe06a18…b5b5

0x34ae4d…3fc5

4 touches
1 conflict

0xd8fd2add…50fc

0x34ae4d…3fc5

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: 0x851145ea…9f3f07

6 conflicts on slot 0xd6265424c9…7b0d3a

← previous block·next block →recent activity