← previous blocknext block →recent activity

Analyzing

Block #98,216,826

35 transactions · 34 stateful · 2026-08-22 14:29:53 UTC

Parallelism

71/100

Blocked

68%

Avg conflicts / tx

2.8

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,216,826  ·  35 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

0x00000000…0002

0xbb3f3c…e046

20 touches
45 conflicts

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

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

45 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity