← previous blocknext block →recent activity

Analyzing

Block #107,838,952

20 transactions · 19 stateful · 2026-09-25 07:56:16 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,838,952  ·  20 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

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0xd6ec332d…1fdb

0x34b655…2a6f

6 touches
3 conflicts

0x70335443…ff8e

0x34b655…2a6f

6 touches
3 conflicts

0x31d88d27…7617

0x34b655…2a6f

6 touches
3 conflicts

0x950f7d79…3cf2

0x851145…3f07

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x1311a526…3132

0x34b655…2a6f

4 touches
1 conflict

0x14fe1598…d0ba

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 0x49890ced8d…316f23

← previous block·next block →recent activity