← previous blocknext block →recent activity

Analyzing

Block #108,664,281

23 transactions · 20 stateful · 2026-09-28 05:10:35 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,664,281  ·  23 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf5dc501b…831c

0x34b655…2a6f

4 touches
1 conflict

0x48203298…65cb

0x34b655…2a6f

4 touches
1 conflict

0x5e28fb66…38cd

0x34b655…2a6f

4 touches
1 conflict

0x6ca15e14…7be8

0x34b655…2a6f

4 touches
1 conflict

0x6f42fec4…4d4a

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 0x482471adbb…39122f

← previous block·next block →recent activity