← previous blocknext block →recent activity

Analyzing

Block #98,850,194

23 transactions · 22 stateful · 2026-08-24 20:12:58 UTC

Parallelism

48/100

Blocked

68%

Avg conflicts / tx

2.52

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #98,850,194  ·  23 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

14 touches
21 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

14 touches
21 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

14 touches
21 conflicts

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xbd590df7…9891

0x34b655…2a6f

12 touches
15 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

12 touches
15 conflicts

0x90e055e8…bcf1

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity