← previous blocknext block →recent activity

Analyzing

Block #99,203,682

19 transactions · 19 stateful · 2026-08-26 01:58:06 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,203,682  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3d93ad2c…e747

0x34b655…2a6f

6 touches
3 conflicts

0xe251ba03…50f8

0x34b655…2a6f

4 touches
1 conflict

0xfcd5e68f…2a12

0x34b655…2a6f

4 touches
1 conflict

0x109d8a52…a7b7

0x34b655…2a6f

4 touches
1 conflict

0x3022fa88…3a51

0x34b655…2a6f

4 touches
1 conflict

0x41c56387…a8f6

0x34b655…2a6f

4 touches
1 conflict

0x7684f61e…fc67

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity