← previous blocknext block →recent activity

Analyzing

Block #99,270,176

24 transactions · 22 stateful · 2026-08-26 07:32:44 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,270,176  ·  24 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x14c4e3ca…edd9

0x34b655…2a6f

4 touches
1 conflict

0x14c4e3ca…edda

0x34b655…2a6f

4 touches
1 conflict

0x2e19029d…72a7

0x34b655…2a6f

4 touches
1 conflict

0x3e6302c8…64f5

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x71fad9ce…c11f

0x34b655…2a6f

4 touches
1 conflict

0x883b1ea6…2acf

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 0xca841faae5…71486a

← previous block·next block →recent activity