← previous blocknext block →recent activity

Analyzing

Block #98,568,470

24 transactions · 19 stateful · 2026-08-23 20:12:31 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,568,470  ·  24 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

0xa9988419…9f45

0x34b655…2a6f

6 touches
3 conflicts

0xd911522b…e960

0x34b655…2a6f

6 touches
3 conflicts

0xabb9f292…17a3

0x34b655…2a6f

6 touches
3 conflicts

0x8a2f9a36…fb4a

0xfa32f9…f3f0

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6ca15e14…7be8

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

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 0xa998841984…609f45

← previous block·next block →recent activity