← previous blocknext block →recent activity

Analyzing

Block #98,276,072

24 transactions · 21 stateful · 2026-08-22 19:27:56 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,276,072  ·  24 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x705a9a1a…db08

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x758a0dd5…0f46

0x34b655…2a6f

4 touches
1 conflict

0x7d91b3f5…3838

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0xac2a0273…721b

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