← previous blocknext block →recent activity

Analyzing

Block #98,605,193

16 transactions · 15 stateful · 2026-08-23 23:23:51 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,605,193  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x080c3a8a…3088

0x34b655…2a6f

4 touches
1 conflict

0x23769ebc…c8ed

0x34b655…2a6f

4 touches
1 conflict

0x5896e8c1…dde5

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x482471adbb…39122f

← previous block·next block →recent activity