← previous blocknext block →recent activity

Analyzing

Block #99,855,593

21 transactions · 20 stateful · 2026-08-28 08:52:41 UTC

Parallelism

48/100

Blocked

55%

Avg conflicts / tx

2.9

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #99,855,593  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x91b13e91…855d

0x34b655…2a6f

22 touches
55 conflicts

0x061c1518…60ea

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xa60eabc0…9f8c

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x23c2d932…4dae

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x85868b0e…a446

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

55 conflicts on slot 0x91b13e914b…cb855d

← previous block·next block →recent activity