← previous blocknext block →recent activity

Analyzing

Block #99,242,765

22 transactions · 18 stateful · 2026-08-26 05:14:45 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,242,765  ·  22 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xfc8d572c…b27d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3f2100d8…f9b5

0xa6afd3…d132

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0xdaf4475b…ff61

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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 0x482471adbb…39122f

← previous block·next block →recent activity