← previous blocknext block →recent activity

Analyzing

Block #99,209,086

23 transactions · 21 stateful · 2026-08-26 02:25:17 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,209,086  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

10 touches
10 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

10 touches
10 conflicts

0xbd590df7…9891

0x34b655…2a6f

10 touches
10 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

8 touches
6 conflicts

0x5d4ae5d8…e4c7

0x34b655…2a6f

6 touches
3 conflicts

0x9771c5e6…5d7b

0x34b655…2a6f

4 touches
1 conflict

0xa70cb615…11da

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity