← previous blocknext block →recent activity

Analyzing

Block #106,252,407

29 transactions · 28 stateful · 2026-09-19 18:47:26 UTC

Parallelism

72/100

Blocked

46%

Avg conflicts / tx

1.66

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,252,407  ·  29 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

0x7cf3eb0f…06c5

0x34b655…2a6f

14 touches
21 conflicts

0xe2ecec55…b797

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x03537d13…069b

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x3e6302c8…64f5

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 0x7cf3eb0f68…8806c5

← previous block·next block →recent activity