← previous blocknext block →recent activity

Analyzing

Block #91,209,787

18 transactions · 17 stateful · 2026-07-29 01:13:18 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,209,787  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7b77cfcd…19b1

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x3b9bb58c…e73a

0x34b655…2a6f

6 touches
3 conflicts

0x30ae635d…5e67

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xb975a8e5…0da2

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 0x7b77cfcd7b…8d19b1

← previous block·next block →recent activity