← previous blocknext block →recent activity

Analyzing

Block #98,778,601

23 transactions · 18 stateful · 2026-08-24 14:12:34 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,778,601  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x295780b7…d2d1

0x34b655…2a6f

4 touches
1 conflict

0x4786839b…c29a

0x34b655…2a6f

4 touches
1 conflict

0x68dfc6ca…56ac

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xaa6f22f7…6a42

0x34b655…2a6f

4 touches
1 conflict

0xab60dc09…85e4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity