← previous blocknext block →recent activity

Analyzing

Block #99,329,796

23 transactions · 18 stateful · 2026-08-26 12:32:37 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,329,796  ·  23 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

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0x554873fd…2ff4

0x34b655…2a6f

4 touches
1 conflict

0x556beb43…e627

0x34b655…2a6f

4 touches
1 conflict

0x5fba4b48…16c0

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x81716ce9…095f

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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 0xe1c4e5ce15…770dec

← previous block·next block →recent activity