← previous blocknext block →recent activity

Analyzing

Block #99,116,918

20 transactions · 16 stateful · 2026-08-25 18:41:30 UTC

Parallelism

85/100

Blocked

44%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,116,918  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xf984d8ab…6e4f

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x24b79a65…9056

0x34b655…2a6f

4 touches
1 conflict

0x705ab4ae…0162

0x34b655…2a6f

4 touches
1 conflict

0x76622fb2…4f08

0x34b655…2a6f

4 touches
1 conflict

0x8641bdc9…7e57

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

3 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity