← previous blocknext block →recent activity

Analyzing

Block #107,642,982

21 transactions · 21 stateful · 2026-09-24 15:28:29 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #107,642,982  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xbd532dec…d7da

0x34b655…2a6f

6 touches
3 conflicts

0x083a8763…5a7b

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x32a4e1a8…89d2

0xd32edf…ff58

5 touches
3 conflicts

0x51fc8795…126f

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 0x42522e76ce…082592

← previous block·next block →recent activity