← previous blocknext block →recent activity

Analyzing

Block #98,275,273

17 transactions · 17 stateful · 2026-08-22 19:23:54 UTC

Parallelism

65/100

Blocked

41%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,275,273  ·  17 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

0xa652b48e…f543

0x34b655…2a6f

8 touches
6 conflicts

0x5d6da397…6c5c

0x34b655…2a6f

8 touches
6 conflicts

0x62030a81…91be

0x34b655…2a6f

6 touches
3 conflicts

0x75e8ccd6…b9de

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0xa048161b…8f4b

0x34b655…2a6f

4 touches
1 conflict

0xf90c6521…d8f0

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

6 conflicts on slot 0xa652b48eee…87f543

← previous block·next block →recent activity