← previous blocknext block →recent activity

Analyzing

Block #92,600,011

18 transactions · 17 stateful · 2026-08-02 21:48:34 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,600,011  ·  18 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

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x989252a1…d812

0xa6afd3…d132

4 touches
1 conflict

0x0672e4a2…8d1f

0x34b655…2a6f

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x5f251b96…6054

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

3 conflicts on slot 0xb4e0a934b9…435fc7

← previous block·next block →recent activity