← previous blocknext block →recent activity

Analyzing

Block #107,817,438

23 transactions · 16 stateful · 2026-09-25 06:07:59 UTC

Parallelism

87/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #107,817,438  ·  23 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

0x1950527a…a8a6

0x34b655…2a6f

6 touches
3 conflicts

0xb15c58ec…bd83

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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 0x1950527a1c…afa8a6

← previous block·next block →recent activity