← previous blocknext block →recent activity

Analyzing

Block #99,606,470

18 transactions · 17 stateful · 2026-08-27 11:50:40 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,606,470  ·  18 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

0x70d81211…f49f

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x1d9154e7…8821

0x34b655…2a6f

4 touches
1 conflict

0x37f0da4a…ff88

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xc16e646d…4fb0

0x34b655…2a6f

4 touches
1 conflict

0xd9c075c9…0a14

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 0x70d812119d…c1f49f

← previous block·next block →recent activity