← previous blocknext block →recent activity

Analyzing

Block #107,785,308

29 transactions · 23 stateful · 2026-09-25 03:26:08 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #107,785,308  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x740fff9f…4244

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x15d50313…d642

0x851145…3f07

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xae7c1880…48a1

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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 0x740fff9f9f…4a4244

← previous block·next block →recent activity