← previous blocknext block →recent activity

Analyzing

Block #91,765,482

16 transactions · 15 stateful · 2026-07-30 23:51:08 UTC

Parallelism

81/100

Blocked

53%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,765,482  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0xd877e706…e9c0

0x34b655…2a6f

4 touches
1 conflict

0x5bdae4ca…5d23

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x97c7aff5…5b68

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

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 0x00ddbbf292…ff4588

← previous block·next block →recent activity