← previous blocknext block →recent activity

Analyzing

Block #91,961,325

17 transactions · 17 stateful · 2026-07-31 16:16:25 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,961,325  ·  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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x11ba6ecb…5b99

0x34b655…2a6f

4 touches
1 conflict

0x24b6091e…d294

0x34b655…2a6f

4 touches
1 conflict

0x2a628ea8…5918

0x851145…3f07

4 touches
1 conflict

0x029cc719…ad33

0x34b655…2a6f

4 touches
1 conflict

0x9ea5c5d8…6813

0x34b655…2a6f

4 touches
1 conflict

0x9ea5c5d8…6814

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity