← previous blocknext block →recent activity

Analyzing

Block #92,370,459

20 transactions · 19 stateful · 2026-08-02 02:34:05 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,370,459  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x1caa030f…26bd

0x34b655…2a6f

8 touches
6 conflicts

0x620b761c…270e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2bb0d58d…9dcf

0x34b655…2a6f

4 touches
1 conflict

0x3093e806…bde2

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

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

10 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity