← previous blocknext block →recent activity

Analyzing

Block #99,457,050

27 transactions · 22 stateful · 2026-08-26 23:13:28 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,457,050  ·  27 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

0xbd22d0fc…64fd

0x34b655…2a6f

6 touches
3 conflicts

0xe97d54c5…ef6f

0x34b655…2a6f

6 touches
3 conflicts

0xfc2493d3…6898

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0xf5a1b40e…5a12

0x34b655…2a6f

4 touches
1 conflict

0x06e7db76…ef34

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 0xbd22d0fc04…0464fd

← previous block·next block →recent activity