← previous blocknext block →recent activity

Analyzing

Block #99,624,785

19 transactions · 18 stateful · 2026-08-27 13:24:44 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,624,785  ·  19 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

0xcc12fbb9…9b45

0x34b655…2a6f

8 touches
6 conflicts

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x8b780b26…f5ff

0x34b655…2a6f

6 touches
3 conflicts

0x7c9f5cc6…985d

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0x938cdab7…6bf5

0x34b655…2a6f

4 touches
1 conflict

0x9c4dd281…689d

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 0xcc12fbb935…f29b45

← previous block·next block →recent activity