← previous blocknext block →recent activity

Analyzing

Block #98,550,020

27 transactions · 20 stateful · 2026-08-23 18:36:07 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,550,020  ·  27 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1a2055c7…9054

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xcc716e47…e524

0x34b655…2a6f

6 touches
3 conflicts

0x5e3014f0…b4e1

0x34b655…2a6f

6 touches
3 conflicts

0x0e2af183…ffa5

0x34b655…2a6f

5 touches
3 conflicts

0xc53799eb…d928

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity