← previous blocknext block →recent activity

Analyzing

Block #105,436,033

20 transactions · 20 stateful · 2026-09-16 22:16:08 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,436,033  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0xe2e74ccf…8a8a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xdc9526ab…def7

0x40c49f…2af0

6 touches
3 conflicts

0x00ec330f…c91a

0x34b655…2a6f

6 touches
3 conflicts

0x0f94e353…1f32

0x34b655…2a6f

6 touches
3 conflicts

0xc10b903d…2f54

0x34b655…2a6f

6 touches
3 conflicts

0xd1448207…452d

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

6 conflicts on slot 0x49890ced8d…316f23

← previous block·next block →recent activity