← previous blocknext block →recent activity

Analyzing

Block #98,087,546

27 transactions · 25 stateful · 2026-08-22 03:38:44 UTC

Parallelism

70/100

Blocked

36%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,087,546  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

6 touches
3 conflicts

0x191cc704…89f4

0x34b655…2a6f

5 touches
3 conflicts

0xea2d3331…6e35

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0007

0x340143…768f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity