← previous blocknext block →recent activity

Analyzing

Block #91,423,242

26 transactions · 20 stateful · 2026-07-29 19:08:34 UTC

Parallelism

62/100

Blocked

60%

Avg conflicts / tx

1.35

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,423,242  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x1bf8d2af…d140

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

8 touches
6 conflicts

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0xaff4d265…d411

0x34b655…2a6f

6 touches
3 conflicts

0x772ab420…c2f6

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 0x1bf8d2afa1…d2d140

← previous block·next block →recent activity