← previous blocknext block →recent activity

Analyzing

Block #98,380,692

28 transactions · 18 stateful · 2026-08-23 04:14:18 UTC

Parallelism

82/100

Blocked

50%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,380,692  ·  28 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

0xb7b16dd0…0426

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x3a921be0…779c

0x2a68ba…90c5

4 touches
1 conflict

0x923b1088…7600

0x40c49f…2af0

4 touches
1 conflict

0x3782b586…0d60

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 0xb7b16dd022…c80426

← previous block·next block →recent activity