← previous blocknext block →recent activity

Analyzing

Block #91,960,208

23 transactions · 18 stateful · 2026-07-31 16:10:47 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,960,208  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x5778d110…d2e6

0xc8689a…ee79

4 touches
1 conflict

0x4e135144…4167

0x34b655…2a6f

4 touches
1 conflict

0x803eb45d…00bd

0x34b655…2a6f

4 touches
1 conflict

0xa20a130c…5d59

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity