← previous blocknext block →recent activity

Analyzing

Block #103,041,365

21 transactions · 20 stateful · 2026-09-08 12:38:18 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #103,041,365  ·  21 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

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xa8590d68…d5c8

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x8c6bf035…4924

0x34b655…2a6f

6 touches
3 conflicts

0x80817ae3…ef38

0x34b655…2a6f

4 touches
1 conflict

0x9aed5849…2f7e

0x34b655…2a6f

4 touches
1 conflict

0x9c2fc330…0091

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity