← previous blocknext block →recent activity

Analyzing

Block #91,417,968

32 transactions · 23 stateful · 2026-07-29 18:42:02 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

0.97

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,417,968  ·  32 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x6077cb2d…4806

0x34b655…2a6f

4 touches
1 conflict

0x69411fb3…e36d

0x34b655…2a6f

4 touches
1 conflict

0x73b0275e…82e9

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbed5ddf9…d1d2

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641d

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

21 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity