← previous blocknext block →recent activity

Analyzing

Block #105,843,940

19 transactions · 18 stateful · 2026-09-18 08:30:33 UTC

Parallelism

47/100

Blocked

61%

Avg conflicts / tx

2.47

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #105,843,940  ·  19 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x5a548af5…0eb0

0x34b655…2a6f

20 touches
45 conflicts

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0xf778799e…2698

0x34b655…2a6f

10 touches
10 conflicts

0x69ba6585…48f4

0x34b655…2a6f

10 touches
10 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

8 touches
6 conflicts

0xf5425ed0…ee68

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 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

45 conflicts on slot 0x5a548af508…f00eb0

← previous block·next block →recent activity