← previous blocknext block →recent activity

Analyzing

Block #105,376,607

22 transactions · 21 stateful · 2026-09-16 17:16:56 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,376,607  ·  22 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

0x7c93b38a…9e69

0x34b655…2a6f

6 touches
3 conflicts

0xf08122ee…d520

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0xab41643c…f9bf

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 0x7c93b38ab4…099e69

← previous block·next block →recent activity