← previous blocknext block →recent activity

Analyzing

Block #108,279,260

17 transactions · 16 stateful · 2026-09-26 20:52:20 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,279,260  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf357bdbb…b9cc

0x34b655…2a6f

4 touches
1 conflict

0xffe2d0c6…b1a6

0x34b655…2a6f

4 touches
1 conflict

0x17c3cde7…2d2e

0x34b655…2a6f

4 touches
1 conflict

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x4073f47e…39e6

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…1266

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity