← previous blocknext block →recent activity

Analyzing

Block #107,817,082

24 transactions · 23 stateful · 2026-09-25 06:06:12 UTC

Parallelism

63/100

Blocked

48%

Avg conflicts / tx

1.67

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #107,817,082  ·  24 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

0x5cf4d55d…c588

0x34b655…2a6f

18 touches
36 conflicts

0xe6341958…a301

0x34b655…2a6f

12 touches
15 conflicts

0x69ee34d1…30f8

0x34b655…2a6f

10 touches
10 conflicts

0x641aed07…bcb9

0x34b655…2a6f

10 touches
10 conflicts

0x8041f328…97e7

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xd25997d0…a68a

0x1b6862…e19c

6 touches
3 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

36 conflicts on slot 0x5cf4d55d39…13c588

← previous block·next block →recent activity