← previous blocknext block →recent activity

Analyzing

Block #98,532,918

25 transactions · 22 stateful · 2026-08-23 17:06:53 UTC

Parallelism

84/100

Blocked

23%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,532,918  ·  25 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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x3945e211…a613

0x34b655…2a6f

6 touches
3 conflicts

0x70e677f5…e3bd

0x34b655…2a6f

6 touches
3 conflicts

0x3750b746…5a9e

0x34b655…2a6f

4 touches
1 conflict

0x49b0842d…0a93

0x34b655…2a6f

4 touches
1 conflict

0x6771eae2…7014

0x34b655…2a6f

4 touches
1 conflict

0x811d5c93…c91a

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 0x737acb7813…fafce8

← previous block·next block →recent activity