← previous blocknext block →recent activity

Analyzing

Block #105,851,461

22 transactions · 20 stateful · 2026-09-18 09:08:25 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,851,461  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x12c00063…cb00

0x34b655…2a6f

12 touches
15 conflicts

0x0efc210e…70ab

0x34b655…2a6f

10 touches
10 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x80398c66…f3cc

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0x46c14e01…ff09

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

15 conflicts on slot 0x12c00063ba…68cb00

← previous block·next block →recent activity