← previous blocknext block →recent activity

Analyzing

Block #98,432,244

27 transactions · 22 stateful · 2026-08-23 08:33:40 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,432,244  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0xcadd9a74…8bb7

0x34b655…2a6f

6 touches
3 conflicts

0x60cbf923…50dd

0x34b655…2a6f

4 touches
1 conflict

0x77c7ce50…0288

0x065c9d…c394

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0x6c2c8c55…bda9

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity