← previous blocknext block →recent activity

Analyzing

Block #105,846,233

20 transactions · 20 stateful · 2026-09-18 08:42:07 UTC

Parallelism

60/100

Blocked

45%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,846,233  ·  20 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

0xb7ce83b1…2c96

0x34b655…2a6f

10 touches
10 conflicts

0x82f1ed07…ff68

0x34b655…2a6f

8 touches
6 conflicts

0x3ba80824…4a64

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x5a548af5…0eb0

0x34b655…2a6f

8 touches
6 conflicts

0x5bdffe1c…2a9e

0x34b655…2a6f

8 touches
6 conflicts

0x60a536a6…ef7a

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

10 conflicts on slot 0xb7ce83b1b6…352c96

← previous block·next block →recent activity