← previous blocknext block →recent activity

Analyzing

Block #98,263,833

19 transactions · 18 stateful · 2026-08-22 18:26:21 UTC

Parallelism

84/100

Blocked

28%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,263,833  ·  19 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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x66300207…c47a

0x99c7a7…8bf0

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xee9a89a2…9fd2

0x34b655…2a6f

4 touches
1 conflict

0x15c6ded9…48e7

0x754704…b603

4 touches
1 conflict

0x5a7e4e98…1f3b

0x754704…b603

4 touches
1 conflict

0xd4c946a4…b8d4

0x754704…b603

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 0x737acb7813…fafce8

← previous block·next block →recent activity