← previous blocknext block →recent activity

Analyzing

Block #107,849,095

21 transactions · 18 stateful · 2026-09-25 08:47:19 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #107,849,095  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xba522812…1f1f

0x34b655…2a6f

6 touches
3 conflicts

0x07fdf9cf…4928

0x34b655…2a6f

4 touches
1 conflict

0x1abfd3ae…2999

0x34b655…2a6f

4 touches
1 conflict

0x36dc68d2…2f3e

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x5e26f4ec…9b6c

0x34b655…2a6f

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

3 conflicts on slot 0xba52281226…3a1f1f

← previous block·next block →recent activity