← previous blocknext block →recent activity

Analyzing

Block #98,848,241

26 transactions · 21 stateful · 2026-08-24 20:03:08 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,848,241  ·  26 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

0x76622fb2…4f08

0x34b655…2a6f

6 touches
3 conflicts

0x54148338…30de

0xd32edf…ff58

5 touches
3 conflicts

0x34724d7a…b996

0x34b655…2a6f

4 touches
1 conflict

0x0f8965bb…e238

0x34b655…2a6f

4 touches
1 conflict

0x62030a81…91be

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcc

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcd

0x34b655…2a6f

4 touches
1 conflict

0x9f8d58b7…a0fc

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 0x76622fb2e3…024f08

← previous block·next block →recent activity