← previous blocknext block →recent activity

Analyzing

Block #105,618,165

21 transactions · 19 stateful · 2026-09-17 13:32:46 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,618,165  ·  21 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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0xc73fd549…2e28

0x851145…3f07

6 touches
3 conflicts

0xdf93c009…d51f

0x851145…3f07

6 touches
3 conflicts

0xdb1e37cb…90c9

0x34b655…2a6f

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: Perpl

3 conflicts on slot 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity