← previous blocknext block →recent activity

Analyzing

Block #99,882,201

19 transactions · 19 stateful · 2026-08-28 11:06:49 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,882,201  ·  19 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

0xcc8b6d32…6601

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x19a9a256…4ba4

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x803fe3bc…be74

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 0xcc8b6d3248…e46601

← previous block·next block →recent activity