← previous blocknext block →recent activity

Analyzing

Block #99,487,219

23 transactions · 22 stateful · 2026-08-27 01:45:24 UTC

Parallelism

78/100

Blocked

32%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,487,219  ·  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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd814f518…f5b4

0x34b655…2a6f

8 touches
6 conflicts

0xac0b4a08…faae

0x34b655…2a6f

6 touches
3 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xc8ab1e9b…ad11

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity