← previous blocknext block →recent activity

Analyzing

Block #98,380,482

18 transactions · 17 stateful · 2026-08-23 04:13:14 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,380,482  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xf4685a69…1b39

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x277af141…8ce5

0x34b655…2a6f

4 touches
1 conflict

0xbd590df7…9891

0x34b655…2a6f

4 touches
1 conflict

0x99bce070…1529

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

← previous block·next block →recent activity