← previous blocknext block →recent activity

Analyzing

Block #98,730,803

31 transactions · 20 stateful · 2026-08-24 10:11:58 UTC

Parallelism

84/100

Blocked

40%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,730,803  ·  31 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x2aab0897…78f7

0x34b655…2a6f

6 touches
3 conflicts

0x3f81bcfb…2905

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x2ea68a12…cc8d

0x34b655…2a6f

4 touches
1 conflict

0x4dbf4de0…2dc2

0x34b655…2a6f

4 touches
1 conflict

0x6d5c5d72…914b

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity