← previous blocknext block →recent activity

Analyzing

Block #107,823,543

21 transactions · 20 stateful · 2026-09-25 06:38:43 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,823,543  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x25144f94…1854

0x34b655…2a6f

6 touches
3 conflicts

0xa2c4d203…05b6

0x34b655…2a6f

6 touches
3 conflicts

0xa7636da9…d6a1

0x34b655…2a6f

6 touches
3 conflicts

0xacd7175d…9381

0x34b655…2a6f

6 touches
3 conflicts

0x232b0b19…d946

0x34b655…2a6f

6 touches
3 conflicts

0x81ca07cc…c115

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

6 conflicts on slot 0x42522e76ce…082592

← previous block·next block →recent activity