← previous blocknext block →recent activity

Analyzing

Block #107,989,821

26 transactions · 24 stateful · 2026-09-25 20:35:44 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.73

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #107,989,821  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xbc8fb280…76a3

0x34b655…2a6f

18 touches
36 conflicts

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0xeb1b4ae8…64bd

0x37db7f…ec7b

12 touches
15 conflicts

0x238d0a65…428b

0x37db7f…ec7b

12 touches
15 conflicts

0x3243e72f…1f6d

0x34b655…2a6f

12 touches
15 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

12 touches
15 conflicts

0x4fb437cc…05f7

0x34b655…2a6f

12 touches
15 conflicts

0x5969523e…5191

0x34b655…2a6f

12 touches
15 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 0xbc8fb28081…2176a3

← previous block·next block →recent activity