← previous blocknext block →recent activity

Analyzing

Block #92,460,540

17 transactions · 17 stateful · 2026-08-02 10:07:04 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,460,540  ·  17 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

0x6f900be0…cd6e

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x9a3068dd…18f1

0x34b655…2a6f

6 touches
3 conflicts

0xb2fa1675…4e07

0x34b655…2a6f

6 touches
3 conflicts

0x427d1120…4eb1

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x88e771e8…7d4a

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0x6f900be04d…4ccd6e

← previous block·next block →recent activity