← previous blocknext block →recent activity

Analyzing

Block #99,854,231

24 transactions · 22 stateful · 2026-08-28 08:45:45 UTC

Parallelism

63/100

Blocked

55%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,854,231  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xc852b267…9d14

0x34b655…2a6f

12 touches
15 conflicts

0x5ad4bb1c…6fa5

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xcdf83c5e…57d4

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x20b94f7c…2a9b

0x34b655…2a6f

6 touches
3 conflicts

0x4387ba94…e195

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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

15 conflicts on slot 0xc852b26715…339d14

← previous block·next block →recent activity