← previous blocknext block →recent activity

Analyzing

Block #104,983,873

20 transactions · 18 stateful · 2026-09-15 08:20:17 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #104,983,873  ·  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

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x157b7af2…12fa

0x34b655…2a6f

4 touches
1 conflict

0x30fbdb35…1259

0x34b655…2a6f

4 touches
1 conflict

0x571a1856…60ce

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x7fd951f1…fe49

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 0xb75367ffdb…6fa2b7

← previous block·next block →recent activity