← previous blocknext block →recent activity

Analyzing

Block #105,932,497

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

Parallelism

54/100

Blocked

52%

Avg conflicts / tx

1.42

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #105,932,497  ·  24 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x12e77486…ec2b

0x34b655…2a6f

6 touches
3 conflicts

0x184e765d…08f6

0x34b655…2a6f

6 touches
3 conflicts

0x309f47c0…e1cf

0x34b655…2a6f

6 touches
3 conflicts

0x3b65c5ca…9f83

0x34b655…2a6f

6 touches
3 conflicts

0x3c9b10c1…d791

0x34b655…2a6f

6 touches
3 conflicts

0x55cde02d…89cb

0x34b655…2a6f

6 touches
3 conflicts

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity