← previous blocknext block →recent activity

Analyzing

Block #99,358,043

19 transactions · 18 stateful · 2026-08-26 14:54:48 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,358,043  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xb240b520…a88a

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xdca5934c…8917

0x34b655…2a6f

6 touches
3 conflicts

0x6e3e9f18…f684

0x34b655…2a6f

6 touches
3 conflicts

0x746bcce3…d0ce

0x34b655…2a6f

4 touches
1 conflict

0x74e46435…fdcd

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

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

6 conflicts on slot 0xb240b520db…67a88a

← previous block·next block →recent activity