← previous blocknext block →recent activity

Analyzing

Block #108,473,016

21 transactions · 20 stateful · 2026-09-27 13:07:27 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,473,016  ·  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

0x260229da…080d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xba9f9225…2ead

0x34b655…2a6f

4 touches
1 conflict

0xcb21158b…f18d

0x34b655…2a6f

4 touches
1 conflict

0xec5b223a…3525

0x34b655…2a6f

4 touches
1 conflict

0xf4461bab…dc70

0x34b655…2a6f

4 touches
1 conflict

0xf51ec09c…b4a9

0x34b655…2a6f

4 touches
1 conflict

0x045532dd…4b7d

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 0x260229dacc…15080d

← previous block·next block →recent activity