← previous blocknext block →recent activity

Analyzing

Block #104,869,754

21 transactions · 20 stateful · 2026-09-14 22:46:03 UTC

Parallelism

71/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,869,754  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbf394a70…2334

0x34b655…2a6f

8 touches
6 conflicts

0xee8237bd…46ad

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x287ab03c…1d20

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x54c6fb44…369a

0x34b655…2a6f

4 touches
1 conflict

0x54f7f60f…43cc

0x34b655…2a6f

4 touches
1 conflict

0x8c387e3e…85b4

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 0xbf394a702c…8a2334

← previous block·next block →recent activity