← previous blocknext block →recent activity

Analyzing

Block #98,325,974

23 transactions · 22 stateful · 2026-08-22 23:39:02 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,325,974  ·  23 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

0x261cbea7…e35e

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35d

0x34b655…2a6f

6 touches
3 conflicts

0x93aff2a7…49a9

0x34b655…2a6f

6 touches
3 conflicts

0xb7b16dd0…0426

0x34b655…2a6f

6 touches
3 conflicts

0x31bb6d7d…904d

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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

3 conflicts on slot 0x261cbea79d…12e35e

← previous block·next block →recent activity