← previous blocknext block →recent activity

Analyzing

Block #91,129,021

46 transactions · 44 stateful · 2026-07-28 18:27:01 UTC

Parallelism

91/100

Blocked

16%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,129,021  ·  46 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbe9baf16…df37

0x34b655…2a6f

8 touches
6 conflicts

0x2aab0897…78f7

0x34b655…2a6f

6 touches
3 conflicts

0xd8b48e27…23a6

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x947bb79d…6458

0x34b655…2a6f

4 touches
1 conflict

0x9f64b79f…6722

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 0xbe9baf16a9…e6df37

← previous block·next block →recent activity