← previous blocknext block →recent activity

Analyzing

Block #98,724,041

18 transactions · 16 stateful · 2026-08-24 09:37:57 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,724,041  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc7ed80d1…56fa

0x40c49f…2af0

9 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

8 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x9d9f3717…44e7

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

2 touches
0 conflicts

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

10 conflicts on slot 0xc7ed80d1e6…8856fa

← previous block·next block →recent activity