← previous blocknext block →recent activity

Analyzing

Block #105,540,341

17 transactions · 17 stateful · 2026-09-17 07:01:02 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,540,341  ·  17 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x9ab4323c…b861

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x81ca8c9e…28cb

0x34b655…2a6f

4 touches
1 conflict

0xe3684e08…c96a

0x34b655…2a6f

4 touches
1 conflict

0xcd93b2d2…30e6

0x34b655…2a6f

4 touches
1 conflict

0x2d360b55…d4fc

0x4ba385…0113

2 touches
0 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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity