← previous blocknext block →recent activity

Analyzing

Block #99,077,814

23 transactions · 17 stateful · 2026-08-25 15:24:29 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,077,814  ·  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

0x731d7308…fd26

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x8488f10f…9354

0x2b46c0…1669

4 touches
1 conflict

0xa17ec269…7cdd

0x2b46c0…1669

4 touches
1 conflict

0xc8525006…2b45

0x2b46c0…1669

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 0x731d73081c…7dfd26

← previous block·next block →recent activity