← previous blocknext block →recent activity

Analyzing

Block #105,849,803

22 transactions · 21 stateful · 2026-09-18 09:00:04 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.18

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,849,803  ·  22 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

0x6caf33e2…c261

0x34b655…2a6f

14 touches
21 conflicts

0xec2a8d79…70cb

0x34b655…2a6f

8 touches
6 conflicts

0x29169c83…348a

0x34b655…2a6f

8 touches
6 conflicts

0x56a78e60…72fb

0x34b655…2a6f

8 touches
6 conflicts

0x4abfb389…18f4

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49dededa…5ce8

0x34b655…2a6f

6 touches
3 conflicts

0x689bcce4…554a

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 0x6caf33e26f…3dc261

← previous block·next block →recent activity