← previous blocknext block →recent activity

Analyzing

Block #105,643,510

21 transactions · 17 stateful · 2026-09-17 15:40:22 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,643,510  ·  21 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

0x9210e826…1414

0x34b655…2a6f

6 touches
3 conflicts

0xd4cee0ab…8844

0xc8689a…ee79

4 touches
1 conflict

0xf0e7ad63…ef51

0x34b655…2a6f

4 touches
1 conflict

0xe148323b…bc6e

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x71587b0a…4a51

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

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 0x9210e826c8…c41414

← previous block·next block →recent activity