← previous blocknext block →recent activity

Analyzing

Block #91,388,301

22 transactions · 20 stateful · 2026-07-29 16:12:25 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1.41

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,388,301  ·  22 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

0x6e6b8ec7…2197

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0ab54c30…b88e

0x34b655…2a6f

6 touches
3 conflicts

0xc492e66a…4af0

0x34b655…2a6f

6 touches
3 conflicts

0xb2195a0c…68ca

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

6 conflicts on slot 0x6e6b8ec76e…cb2197

← previous block·next block →recent activity