← previous blocknext block →recent activity

Analyzing

Block #99,198,413

17 transactions · 17 stateful · 2026-08-26 01:31:36 UTC

Parallelism

41/100

Blocked

59%

Avg conflicts / tx

2.71

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #99,198,413  ·  17 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

14 touches
21 conflicts

0xbd590df7…9891

0x34b655…2a6f

14 touches
21 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

14 touches
21 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

14 touches
21 conflicts

0x81e1f4e8…08d7

0x34b655…2a6f

10 touches
10 conflicts

0x825f9b19…8669

0x34b655…2a6f

9 touches
10 conflicts

0xf620f2c4…773e

0x34b655…2a6f

7 touches
6 conflicts

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

45 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity