← previous blocknext block →recent activity

Analyzing

Block #99,503,335

19 transactions · 18 stateful · 2026-08-27 03:06:31 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,503,335  ·  19 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

0xc406fe27…9ab2

0x34b655…2a6f

6 touches
3 conflicts

0xdd6538fb…2b3f

0x34b655…2a6f

6 touches
3 conflicts

0x5b09bf44…5907

0xa6afd3…d132

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xc95f91db…a901

0x34b655…2a6f

4 touches
1 conflict

0xd2862d04…388c

0x34b655…2a6f

4 touches
1 conflict

0xeb098ed1…f36f

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 0xc406fe277a…629ab2

← previous block·next block →recent activity