← previous blocknext block →recent activity

Analyzing

Block #107,812,846

21 transactions · 18 stateful · 2026-09-25 05:44:53 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.29

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,812,846  ·  21 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

0x740fff9f…4244

0x34b655…2a6f

10 touches
10 conflicts

0x49890ced…6f23

0x34b655…2a6f

10 touches
10 conflicts

0x88188d2d…2a76

0x34b655…2a6f

8 touches
6 conflicts

0x302767c5…403f

0x34b655…2a6f

8 touches
6 conflicts

0xf27c90db…4580

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x2b76a1fb…fdfc

0x34b655…2a6f

8 touches
6 conflicts

0xf51ec09c…b4a9

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

← previous block·next block →recent activity