← previous blocknext block →recent activity

Analyzing

Block #105,843,891

23 transactions · 23 stateful · 2026-09-18 08:30:18 UTC

Parallelism

65/100

Blocked

43%

Avg conflicts / tx

1.39

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,843,891  ·  23 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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x27e92642…b1c1

0x34b655…2a6f

8 touches
6 conflicts

0x5a548af5…0eb0

0x34b655…2a6f

8 touches
6 conflicts

0x3aed8a17…20f9

0x34b655…2a6f

8 touches
6 conflicts

0x6a6c869d…e3b1

0x34b655…2a6f

8 touches
6 conflicts

0xa6d40b7f…2969

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity