← previous blocknext block →recent activity

Analyzing

Block #99,097,663

18 transactions · 18 stateful · 2026-08-25 17:04:38 UTC

Parallelism

67/100

Blocked

39%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,097,663  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x76622fb2…4f08

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x295780b7…d2d1

0x34b655…2a6f

4 touches
1 conflict

0x30ae635d…5e67

0x34b655…2a6f

4 touches
1 conflict

0x773c2bd8…6f32

0x34b655…2a6f

4 touches
1 conflict

0x7a4885a1…e7e3

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity