← previous blocknext block →recent activity

Analyzing

Block #99,367,031

20 transactions · 17 stateful · 2026-08-26 15:40:11 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,367,031  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x37b1078b…e857

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49b0842d…0a93

0x34b655…2a6f

4 touches
1 conflict

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x4f4d8ea3…9d90

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

3 conflicts on slot 0x68531239f9…5ae9a3

← previous block·next block →recent activity