← previous blocknext block →recent activity

Analyzing

Block #105,575,938

25 transactions · 23 stateful · 2026-09-17 10:00:12 UTC

Parallelism

72/100

Blocked

48%

Avg conflicts / tx

1.08

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,575,938  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc5847c4d…a65c

0x34b655…2a6f

14 touches
21 conflicts

0x2179de6a…26d0

0x34b655…2a6f

12 touches
15 conflicts

0xc10b903d…2f54

0x34b655…2a6f

8 touches
6 conflicts

0xf90c6521…d8f0

0x34b655…2a6f

8 touches
6 conflicts

0x4ab195e7…0967

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x693badd1…0fa5

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 0xc5847c4d32…49a65c

← previous block·next block →recent activity