← previous blocknext block →recent activity

Analyzing

Block #98,753,329

22 transactions · 20 stateful · 2026-08-24 12:05:20 UTC

Parallelism

68/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,753,329  ·  22 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

0xe7ad475a…0e41

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xa6855ed4…cf1c

0x34b655…2a6f

4 touches
1 conflict

0xaa179075…fdee

0x34b655…2a6f

4 touches
1 conflict

0xac808a27…82db

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 0xe7ad475a4a…4e0e41

← previous block·next block →recent activity