← previous blocknext block →recent activity

Analyzing

Block #92,857,079

18 transactions · 18 stateful · 2026-08-03 19:22:59 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,857,079  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xb1d30b59…529f

0x34b655…2a6f

8 touches
6 conflicts

0xb39cb1d8…effa

0x34b655…2a6f

6 touches
3 conflicts

0x338e35bb…81b0

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37a

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0x5e649ea2…4206

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 0xc824469a90…af6425

← previous block·next block →recent activity