← previous blocknext block →recent activity

Analyzing

Block #91,254,833

23 transactions · 18 stateful · 2026-07-29 05:00:00 UTC

Parallelism

91/100

Blocked

33%

Avg conflicts / tx

0.26

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,254,833  ·  23 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xda27c764…7fab

0x34b655…2a6f

4 touches
1 conflict

0xe3240f06…2d89

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x6edce976…dedb

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

1 conflict on slot 0xac2a02739b…81721b

← previous block·next block →recent activity