← previous blocknext block →recent activity

Analyzing

Block #91,422,565

16 transactions · 16 stateful · 2026-07-29 19:05:10 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,422,565  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x41bd9bd2…64d8

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0xcc351d6d…256b

0x34b655…2a6f

6 touches
3 conflicts

0xe3e6c02a…d3d4

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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 0x41bd9bd2f3…1b64d8

← previous block·next block →recent activity