← previous blocknext block →recent activity

Analyzing

Block #98,914,222

22 transactions · 19 stateful · 2026-08-25 01:35:04 UTC

Parallelism

50/100

Blocked

53%

Avg conflicts / tx

2.05

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #98,914,222  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

18 touches
36 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xb409e204…89ac

0x34b655…2a6f

8 touches
6 conflicts

0xbd590df7…9891

0x34b655…2a6f

4 touches
1 conflict

0x20b94f7c…2a9b

0x34b655…2a6f

4 touches
1 conflict

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity