← previous blocknext block →recent activity

Analyzing

Block #91,386,260

17 transactions · 15 stateful · 2026-07-29 16:02:09 UTC

Parallelism

47/100

Blocked

67%

Avg conflicts / tx

1.53

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,386,260  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x0ab54c30…b88e

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x3a15404b…10b1

0x34b655…2a6f

4 touches
1 conflict

0x4e782273…1690

0x34b655…2a6f

4 touches
1 conflict

0x6e6b8ec7…2197

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

10 conflicts on slot 0x0ab54c30a6…82b88e

← previous block·next block →recent activity