← previous blocknext block →recent activity

Analyzing

Block #98,651,668

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

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,651,668  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xe83d589b…c7c6

0x40c49f…2af0

4 touches
1 conflict

0xceeccdea…51dc

0x40c49f…2af0

4 touches
1 conflict

0x91621901…2aa7

0x40c49f…2af0

4 touches
1 conflict

0x1408e7c7…f324

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x961c0cd9…0937

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity