← previous blocknext block →recent activity

Analyzing

Block #99,367,027

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

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,367,027  ·  26 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

8 touches
6 conflicts

0x465fa0a0…01c6

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x49b0842d…0a93

0x34b655…2a6f

4 touches
1 conflict

0x37b1078b…e857

0x34b655…2a6f

4 touches
1 conflict

0x671327de…0812

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x68531239f9…5ae9a3

← previous block·next block →recent activity