← previous blocknext block →recent activity

Analyzing

Block #105,855,443

20 transactions · 19 stateful · 2026-09-18 09:28:28 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,855,443  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x9dccd2a9…2790

0x34b655…2a6f

14 touches
21 conflicts

0x45d57a39…64cf

0x34b655…2a6f

12 touches
15 conflicts

0x5b6af007…0f35

0x34b655…2a6f

8 touches
6 conflicts

0x0efc210e…70ab

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0xa6430862…7971

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

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 0xc824469a90…af6425

← previous block·next block →recent activity