← previous blocknext block →recent activity

Analyzing

Block #98,838,736

20 transactions · 20 stateful · 2026-08-24 19:15:19 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,838,736  ·  20 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

0xaf831072…51d6

0x69a5f9…2fef

8 touches
6 conflicts

0xaf831072…51dc

0x69a5f9…2fef

8 touches
6 conflicts

0x2ef1d89b…196d

0x754704…b603

8 touches
6 conflicts

0x00000000…0036

0x35a73b…6042

8 touches
6 conflicts

0xaf831072…51d5

0x69a5f9…2fef

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x2ad2f4bc…1800

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: 0x69a5f9ad…102fef

6 conflicts on slot 0xaf831072f6…c551d6

← previous block·next block →recent activity