← previous blocknext block →recent activity

Analyzing

Block #99,184,808

32 transactions · 24 stateful · 2026-08-26 00:23:08 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.34

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,184,808  ·  32 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x746bcce3…d0ce

0x34b655…2a6f

6 touches
3 conflicts

0x587c3223…8560

0x34b655…2a6f

6 touches
3 conflicts

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x3e2691ca…da1c

0x34b655…2a6f

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x6713b018…05f3

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

3 conflicts on slot 0x746bcce3fa…c7d0ce

← previous block·next block →recent activity