← previous blocknext block →recent activity

Analyzing

Block #91,432,038

19 transactions · 18 stateful · 2026-07-29 19:53:43 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,432,038  ·  19 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

0x8722ac78…9cfc

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x92115abd…ad76

0x34b655…2a6f

6 touches
3 conflicts

0x966e45cf…0f25

0x34b655…2a6f

6 touches
3 conflicts

0x529e53cf…38e4

0xa6afd3…d132

4 touches
1 conflict

0xc6b1d981…1be2

0xa6afd3…d132

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

6 conflicts on slot 0x8722ac78ce…089cfc

← previous block·next block →recent activity