← previous blocknext block →recent activity

Analyzing

Block #99,974,944

17 transactions · 17 stateful · 2026-08-28 18:54:10 UTC

Parallelism

82/100

Blocked

47%

Avg conflicts / tx

0.59

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,974,944  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6dedaff6…161b

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2d94df5e…b193

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x62910921…3016

0x34b655…2a6f

4 touches
1 conflict

0x66c60170…9264

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 0x6dedaff684…2d161b

← previous block·next block →recent activity