← previous blocknext block →recent activity

Analyzing

Block #98,527,832

18 transactions · 17 stateful · 2026-08-23 16:40:28 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,527,832  ·  18 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

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x25387253…1397

0x40c49f…2af0

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x3e0f56fb…e78f

0x34b655…2a6f

4 touches
1 conflict

0xb9508f7d…23a3

0x40c49f…2af0

4 touches
1 conflict

0x5639618d…6388

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 0x801a6e5726…c1d85c

← previous block·next block →recent activity