← previous blocknext block →recent activity

Analyzing

Block #98,064,199

17 transactions · 16 stateful · 2026-08-22 01:41:14 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,064,199  ·  17 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

0x3836a730…b3a9

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x2a5499c6…0abf

0xa6afd3…d132

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x94710b77…a921

0x34b655…2a6f

4 touches
1 conflict

0xcfdec541…94c5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

6 conflicts on slot 0x3836a73066…21b3a9

← previous block·next block →recent activity