← previous blocknext block →recent activity

Analyzing

Block #98,428,307

27 transactions · 22 stateful · 2026-08-23 08:13:51 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,428,307  ·  27 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0x62910921…3016

0x34b655…2a6f

4 touches
1 conflict

0x742f5bb8…594d

0x34b655…2a6f

4 touches
1 conflict

0x7c82b710…e9a9

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x9660902a…a12b

0x34b655…2a6f

4 touches
1 conflict

0xa80684c9…3948

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 0xca841faae5…71486a

← previous block·next block →recent activity