← previous blocknext block →recent activity

Analyzing

Block #98,848,298

19 transactions · 18 stateful · 2026-08-24 20:03:25 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,848,298  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xfcbe8228…8938

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x41335ddf…94b9

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 0xf3d10975b0…050d07

← previous block·next block →recent activity