← previous blocknext block →recent activity

Analyzing

Block #98,678,269

21 transactions · 19 stateful · 2026-08-24 05:44:23 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,678,269  ·  21 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

0x3ae169e4…6c79

0x40c49f…2af0

6 touches
3 conflicts

0xc4d98fb1…c354

0x40c49f…2af0

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xfa5e4695…9356

0x40c49f…2af0

5 touches
3 conflicts

0xce1efe70…2ec8

0x2b46c0…1669

4 touches
1 conflict

0xe49b1b9b…0be1

0x2b46c0…1669

4 touches
1 conflict

0x1c389468…6b0e

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: 0x40c49f17…d22af0

3 conflicts on slot 0x3ae169e47d…d96c79

← previous block·next block →recent activity