← previous blocknext block →recent activity

Analyzing

Block #98,998,907

38 transactions · 21 stateful · 2026-08-25 08:41:24 UTC

Parallelism

82/100

Blocked

48%

Avg conflicts / tx

0.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,998,907  ·  38 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

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x5b842fa7…badd

0x3bd359…433a

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

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity