← previous blocknext block →recent activity

Analyzing

Block #98,778,848

18 transactions · 18 stateful · 2026-08-24 14:13:48 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,778,848  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x042ca3c7…8d1d

0x34b655…2a6f

6 touches
3 conflicts

0x6d1b72ee…6b78

0x34b655…2a6f

6 touches
3 conflicts

0x66300207…c47a

0x99c7a7…8bf0

4 touches
1 conflict

0x15c6ded9…48e7

0x754704…b603

4 touches
1 conflict

0x5a7e4e98…1f3b

0x754704…b603

4 touches
1 conflict

0x8401a9f1…e868

0x754704…b603

4 touches
1 conflict

0x45436af6…437f

0x99c7a7…8bf0

4 touches
1 conflict

0x482471ad…122f

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 0x042ca3c7b4…068d1d

← previous block·next block →recent activity