← previous blocknext block →recent activity

Analyzing

Block #107,849,220

23 transactions · 21 stateful · 2026-09-25 08:47:57 UTC

Parallelism

65/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,849,220  ·  23 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

0x49890ced…6f23

0x34b655…2a6f

12 touches
15 conflicts

0x94b6efbd…d34a

0x34b655…2a6f

10 touches
10 conflicts

0xba522812…1f1f

0x34b655…2a6f

10 touches
10 conflicts

0x6b267bdf…b173

0x34b655…2a6f

10 touches
10 conflicts

0x3a0850ba…c5fa

0x34b655…2a6f

8 touches
6 conflicts

0x2029b74e…c206

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c6

0x1b6862…e19c

4 touches
1 conflict

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

15 conflicts on slot 0x49890ced8d…316f23

← previous block·next block →recent activity