← previous blocknext block →recent activity

Analyzing

Block #98,262,764

17 transactions · 11 stateful · 2026-08-22 18:20:59 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,262,764  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x31d88d27…7617

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x5d1ac445…5233

0x34b655…2a6f

4 touches
1 conflict

0x5d6da397…6c5c

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