← previous blocknext block →recent activity

Analyzing

Block #91,425,041

13 transactions · 12 stateful · 2026-07-29 19:18:26 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,425,041  ·  13 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x6a29db4f…953a

0x34b655…2a6f

4 touches
1 conflict

0x6fbc2e5a…e69c

0x34b655…2a6f

4 touches
1 conflict

0x7c93b38a…9e69

0x34b655…2a6f

4 touches
1 conflict

0xb71dd8e4…16ae

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity