← previous blocknext block →recent activity

Analyzing

Block #90,603,957

21 transactions · 15 stateful · 2026-07-26 22:24:31 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,603,957  ·  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

0xa164d951…1534

0xe1c8b7…3022

6 touches
3 conflicts

0x33e1047c…f65a

0x9f3832…4ae4

6 touches
3 conflicts

0x7cf5136f…ba69

0x9f3832…4ae4

6 touches
3 conflicts

0xa4b7c8aa…4596

0x9f3832…4ae4

6 touches
3 conflicts

0xa4b7c8aa…4597

0x9f3832…4ae4

6 touches
3 conflicts

0x53bc68ea…13ad

0xe1c8b7…3022

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x917f99a5…7989

0x34b655…2a6f

6 touches
3 conflicts

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: 0xe1c8b733…e33022

3 conflicts on slot 0xa164d95170…fa1534

← previous block·next block →recent activity