← previous blocknext block →recent activity

Analyzing

Block #91,437,870

19 transactions · 18 stateful · 2026-07-29 20:23:03 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,437,870  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x88f36c84…929d

0x34b655…2a6f

6 touches
3 conflicts

0x0672e4a2…8d1f

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

4 touches
1 conflict

0x155e52ca…fac7

0x34b655…2a6f

4 touches
1 conflict

0x2f8f103b…29f4

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x503d17fc…e0a9

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 0x88f36c8497…00929d

← previous block·next block →recent activity