← previous blocknext block →recent activity

Analyzing

Block #91,981,602

21 transactions · 19 stateful · 2026-07-31 17:58:23 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,981,602  ·  21 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x766a9366…8da1

0x34b655…2a6f

6 touches
3 conflicts

0x2029b74e…c206

0x34b655…2a6f

4 touches
1 conflict

0x2e1f5171…ad2d

0x34b655…2a6f

4 touches
1 conflict

0x4acbdbcf…a8c6

0x34b655…2a6f

4 touches
1 conflict

0x521a91b0…b4c9

0x34b655…2a6f

4 touches
1 conflict

0x5b30a6e6…b249

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity