← previous blocknext block →recent activity

Analyzing

Block #91,211,718

21 transactions · 20 stateful · 2026-07-29 01:23:00 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,211,718  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x2be02b4b…59de

0x34b655…2a6f

4 touches
1 conflict

0x418f6232…2de6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5a310d83…cae0

0x34b655…2a6f

4 touches
1 conflict

0x65977bc0…2640

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity