← previous blocknext block →recent activity

Analyzing

Block #99,288,013

17 transactions · 17 stateful · 2026-08-26 09:02:27 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,288,013  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x6eff310a…c34c

0x2b46c0…1669

4 touches
1 conflict

0xb55a7cbc…68f5

0x2b46c0…1669

4 touches
1 conflict

0xbbca528a…1b10

0x2b46c0…1669

4 touches
1 conflict

0xe49b1b9b…0be1

0x2b46c0…1669

4 touches
1 conflict

0x1db5837f…1264

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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: 0x40c49f17…d22af0

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity