← previous blocknext block →recent activity

Analyzing

Block #105,922,614

21 transactions · 17 stateful · 2026-09-18 15:07:24 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,922,614  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

6 touches
3 conflicts

0xd874dcbe…381c

0x34b655…2a6f

6 touches
3 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

6 touches
3 conflicts

0x309f47c0…e1cf

0x34b655…2a6f

4 touches
1 conflict

0x3b65c5ca…9f83

0x34b655…2a6f

4 touches
1 conflict

0x3c9b10c1…d791

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity