← previous blocknext block →recent activity

Analyzing

Block #99,367,011

31 transactions · 23 stateful · 2026-08-26 15:40:05 UTC

Parallelism

84/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,367,011  ·  31 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

0x68531239…e9a3

0x34b655…2a6f

10 touches
10 conflicts

0x8db32935…81a7

0x34b655…2a6f

6 touches
3 conflicts

0x44c9cb1f…59b3

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x72083f0d…082a

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

10 conflicts on slot 0x68531239f9…5ae9a3

← previous block·next block →recent activity