← previous blocknext block →recent activity

Analyzing

Block #99,487,329

23 transactions · 22 stateful · 2026-08-27 01:45:57 UTC

Parallelism

70/100

Blocked

36%

Avg conflicts / tx

0.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,487,329  ·  23 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x8b7fe709…9d99

0x34b655…2a6f

8 touches
6 conflicts

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x7b67f6cf…0aab

0x34b655…2a6f

4 touches
1 conflict

0xa1731f0f…1f9d

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity