← previous blocknext block →recent activity

Analyzing

Block #98,439,607

23 transactions · 23 stateful · 2026-08-23 09:10:42 UTC

Parallelism

70/100

Blocked

65%

Avg conflicts / tx

1.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,439,607  ·  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

0x00000000…0002

0xbb3f3c…e046

14 touches
21 conflicts

0xfda39b6f…d4cc

0x754704…b603

8 touches
6 conflicts

0x00000000…0036

0x35a73b…6042

8 touches
6 conflicts

0xaf831072…51dc

0x69a5f9…2fef

8 touches
6 conflicts

0xaf831072…51d6

0x69a5f9…2fef

8 touches
6 conflicts

0xaf831072…51d5

0x69a5f9…2fef

8 touches
6 conflicts

0x2ef1d89b…196d

0x754704…b603

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

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: 0xbb3f3cb7…74e046

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity