← previous blocknext block →recent activity

Analyzing

Block #90,977,272

14 transactions · 14 stateful · 2026-07-28 05:42:40 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,977,272  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x1d67da29…8dce

0x34b655…2a6f

4 touches
1 conflict

0x2464f36f…724c

0x34b655…2a6f

4 touches
1 conflict

0x6c26d635…1bbf

0x34b655…2a6f

4 touches
1 conflict

0x70b7b52e…7743

0x34b655…2a6f

4 touches
1 conflict

0x818e1296…f4d7

0x34b655…2a6f

4 touches
1 conflict

0x86a2e799…7474

0x34b655…2a6f

4 touches
1 conflict

0xa3ed5a09…c6d3

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 0x482471adbb…39122f

← previous block·next block →recent activity