← previous blocknext block →recent activity

Analyzing

Block #91,431,712

23 transactions · 20 stateful · 2026-07-29 19:52:04 UTC

Parallelism

78/100

Blocked

40%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,431,712  ·  23 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

0x4ec9ff52…e6f7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x420dd604…6879

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x92115abd…ad76

0x34b655…2a6f

4 touches
1 conflict

0x966e45cf…0f25

0x34b655…2a6f

4 touches
1 conflict

0xab41643c…f9bf

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 0x4ec9ff52ce…67e6f7

← previous block·next block →recent activity