← previous blocknext block →recent activity

Analyzing

Block #105,845,079

17 transactions · 17 stateful · 2026-09-18 08:36:16 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,845,079  ·  17 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

0xfd7f5b55…4994

0x34b655…2a6f

6 touches
3 conflicts

0x90a021f0…f922

0x34b655…2a6f

4 touches
1 conflict

0xab707260…67d6

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x6183ee9a…21b1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x20cc2272…88dc

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 0xfd7f5b557f…f74994

← previous block·next block →recent activity