← previous blocknext block →recent activity

Analyzing

Block #90,834,174

14 transactions · 11 stateful · 2026-07-27 17:42:48 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,834,174  ·  14 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

0x15554b7b…e30e

0x34b655…2a6f

4 touches
1 conflict

0x3e0065ad…e39b

0x34b655…2a6f

4 touches
1 conflict

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0x4f893478…c649

0x34b655…2a6f

4 touches
1 conflict

0x57592e2a…53b9

0x34b655…2a6f

4 touches
1 conflict

0x5e2ea201…12de

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x7b0665e8…fbdf

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 0x15554b7bbd…2fe30e

← previous block·next block →recent activity