← previous blocknext block →recent activity

Analyzing

Block #99,490,656

21 transactions · 21 stateful · 2026-08-27 02:02:42 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,490,656  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc6b65f73…ab6d

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x5c455afd…ce06

0x34b655…2a6f

8 touches
6 conflicts

0xe098738f…9bbe

0x34b655…2a6f

6 touches
3 conflicts

0xd1b40f29…9b9d

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x81ca8c9e…28cb

0x34b655…2a6f

6 touches
3 conflicts

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 0xc6b65f73e1…b7ab6d

← previous block·next block →recent activity