← previous blocknext block →recent activity

Analyzing

Block #99,959,357

22 transactions · 15 stateful · 2026-08-28 17:35:39 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,959,357  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xd97b0449…00a0

0x34b655…2a6f

4 touches
1 conflict

0xab2b11cd…7e41

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xf5dc501b…8313

0x34b655…2a6f

4 touches
1 conflict

0xfe770323…579f

0x34b655…2a6f

4 touches
1 conflict

0x4c29ecd5…58b6

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity